Share via

Что такое репро шаги?

  • Article

Раскрою немного внутреннюю кухню службы поддержки.

Репро шаги - это шаги воспроизведения проблемы на стандартной системе. Это тот материал, на который опираются тестеры, разработчики, аналитики (рабочим языком для этих команд является Английский). В репро шагах так же указываются текущие и ожидаемые результаты.

Пример репро шагов:
---
STEPS TO REPRO
1-Install NAV 2009 R2 (W1) from distribution disk // Install Demo
// Open Microsoft SQL Server Management Studio, check that database Demo Database NAV (6-0) has been added.
2-Open RTC (NAV 2009) interface run report Prod. Order - Job Card (99000762) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Time Needed” = 134 MINUTES
3-Open RTC interface run report Prod. Order - Precalc. Time (99000764) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Expected Capacity Need” = 134
4-Go to Services (Control Panel…), find Microsoft Dynamics NAV Server, stop it
5-Install NAV 2013 (W1) from distribution disk // Installation option Developer, set SQL Server Instance to empty
// Open Microsoft SQL Server Management Studio, check that database Demo Database NAV (7-0) has been added.
6-Run NAV 2013 Development Environment (use 7-0 database), select all objects and export the objects to Objects70.fob
7-Open Classic (NAV 2009, SQL Option) interface, open database Demo Database NAV (6-0)
8-Import (replace All) the Upgrade601700.1.fob file // take file from distribution disk, ..\UpgradeToolKit\Data Conversion Tools\601
9-Classic (NAV 2009, SQL Option) interface, Form 104001, Upgrade - Old Version, Choose Transfer Data
10-Classic (NAV 2009, SQL Option) interface, Form 104001, Upgrade - Old Version, Choose Delete Objects
11-Close NAV
12-Open Microsoft SQL Server Management Studio, select database Demo Database NAV (6-0), Properties, Options, set Compatibility Level (110) // in repro use SQL Server 2012
13-Open Microsoft SQL Server Management Studio, select database Demo Database NAV (6-0), Security, Users, select NT AUTHORITY\NETWORK SERVICE, Membership, set
db_datareader
db_datawriter
db_ddladmin
db_owner
14-Run NAV 2013 Development Environment select database Demo Database NAV (6-0) // database converted
15-Close NAV
16-Go to Services (Control Panel…), find Microsoft Dynamics NAV Server [DynamicsNAV70], stop it
17-Start the Microsoft Dynamics NAV Server Administration tool and select DynamicsNAV70 instance in the left pane.
Choose the Edit button at the bottom of the settings list in the center pane and update Database Name = Demo Database NAV (6-0). Choose the Save button when you are finished.
18-Go to Services (Control Panel…), find Microsoft Dynamics NAV Server [DynamicsNAV70], start it
19-Run NAV 2013 Development Environment select database Demo Database NAV (6-0)
20-Using Object Designer, import (replace All) Objects70.fob (step 6) into the database
21-Compile all objects
22-Import (replace All) the Upgrade601700.2.fob file // take file distribution disk,..\NAV2013_W1\UpgradeToolKit\Data Conversion Tools\601
23-Run page 104002, Upgrade - New Version.
Check the value for SQL Server Name. If the value is incorrect, update it.
Choose Test Database Connection to verify the connection.
In the Upgrade - New Version page, choose Transfer Data (…select Allow).
24-Close NAV
25-Run NAV 2013 Development Environment select database Demo Database NAV (6-0), Run codeunit 2, Company-Initialize
26-Close NAV
27-Open NAV 2013 client run report Prod. Order - Job Card (99000762) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Time Needed” = 0.00223 MINUTES (!)
28-Open NAV 2013 client run report Prod. Order - Precalc. Time (99000764) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Expected Capacity Need” = 0.00223 (!)
29-Run NAV 2013 Development Environment select database Demo Database NAV (6-0), Run table 5409 (Prod. Order Routing Line), first line “Expected Capacity Need” = 134 (!) // this line relate to 109001 Production Order
30-Run NAV 2013 Development Environment select database Demo Database NAV (6-0), Run table 5410 (Prod. Order Capacity Need),
first line “Needed Time” = 24, “Needed Time (ms)” = 0 (!) // this line relate to 109001 Production Order
second line “Needed Time” = 110, “Needed Time (ms)” = 0 (!) // this line relate to 109001 Production Order

Additional check (If refresh Production Order then system show right result)

31-Open NAV 2013 client. Go to ‘Planned Production Order’ (109001), Refresh Production Order
32-Run NAV 2013 Development Environment select database Demo Database NAV (6-0), Run table 5409 (Prod. Order Routing Line), first line “Expected Capacity Need” = 8 040 000
33-Run NAV 2013 Development Environment select database Demo Database NAV (6-0), Run table 5410 (Prod. Order Capacity Need),
first line “Needed Time” = 24, “Needed Time (ms)” = 1 440 000
second line “Needed Time” = 110, “Needed Time (ms)” = 6 600 000
34-Open NAV 2013 client, run report Prod. Order - Job Card (99000762) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Time Needed” = 134 MINUTES
35-Open NAV 2013 client, run report Prod. Order - Precalc. Time (99000764) // CRONUS International Ltd./Departments/Manufacturing/Execution/
Set filter
- “Status” = Planned
- “No.” = 109001
As result we can see for Operation No. = 10 
- “Expected Capacity Need” = 134

ACTUAL RESULTS
Upgrade Toolkit (NAV 2009 -> NAV 2013) does not convert field Expected Capacity Need to milliseconds and do not fill new field Needed Time (ms).

PARTNER EXPECTED RESULTS (Customer / Partner / SP)
Upgrade Toolkit (NAV 2009 -> NAV 2013) should convert field Expected Capacity Need to milliseconds and do not fill new field Needed Time (ms).

// If Refresh Production Orders then system show the right results but in any case good idea fix the issue in Upgrade Toolkit.
---