Revision History

You might also like

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 30

Revision History

Rev. No. Date


Section No. Changed Change Description Author
(X.YY) (YYYY-MM-DD)
0.01 2022-01-20 All Initialize file
0.02 2022-02-14 All Update following new schedule

0.03 2022-03-08 All Update test result round 1 at MC


Reviewed
Approved by
by
1. Definition of test at customer's side (the same )
1. Functions: High priority
1. Check functions that work with hardware
2. Check functions that work with tables of
3. Check functions that work with other software: ….
4. Check functions that use .csv file from customer if have
5. Check similar bugs (….
+ GUI broken
+ Connection to Xray Viewer
+ Inconsistent master data with TDSL: terminal_division
6. Check GUI of all functions (only 1 test cases for each functions)

2. Functions: Medium or Low priority


1. Setting function

3. Test cases: High priority


1. Must test to confirm the working of functions with other sides

4. Test cases: Medium or Low priority


1. Scenario is already covered by test cases with High priority
2. Check more details in some differenct cases

2. Test strategy:
# Option Test with functions Test with test cases Round 1 Round 2 Work on Saturday Pros & Cons
1 Test plan 1 High High Test all of TCs Check impacted function NO Pros:
….. Medium - Reduce risk about delay hardware
Low - Also can cover bug from low and medium test cases if
any
Cons:
- Need support from Dai-san. Pending AGV work.
- Delay can be occurred if have some problem with the
hardware

2 Test plan 2 High High Test all of TC with high & Check impacted function NO Pros:
…... Medium medium priority - Reduce workload
Cons:
- Hidden bug from un-test test cases

We will follow customs project, executed testing for all of the test cases at customer's side

3. Testing scope
Customs Total of test cases Test at TSDV Test at Bubaigawara Test at customer side Remak
(STS document)
TSDV:
+ Execute all of test cases
cc:
+ Only execute high priority test cases of high priority functions
1153 334 1153 cc:
Nagoya 1153
(Done) (Done) (Done) + Execute all of test cases again at customer side

Osaka 957 957 957


(Done)

Moji 920 920 920


(Done)
Remark
Test Classification
Test Set
High Medium Low
5.2. User authentication 6 16 0
5.2. Common functions 8 12 0
5.3. First inspection 47 22 0
5.4. Second inspection 76 49 0
5.5.2. Parcel search 43 37 0
5.5.3. Data Extraction 28 36 0
5.5.4. Data summarization 30 52 2
5.5.5. Chute setting 9 0 0
5.5.6. Power management 18 5 0
5.5.7. EAD Management 22 23 0
5.5.8. OCR Management 21 14 0
5.5.9. User management 21 2 0
5.5.10. Risk country 16 3 0
5.5.11. System status display 12 92 0
5.5.12. Log management 14 52 0
5.5.13. Cron-job 32 9 0
6. Show X-ray image 7 20 0
7. Combination 38 2 0
8. Non-functional 24 0 0
SUM 472 446 2
Execution time 47.2 44.6 0.2
Total Execution time 92.0
Effort
Priority Test
(Hour)
Low Yes 2.2
Medium Yes 2
High Yes 6.9
Medium Yes 12.5
High Yes 8
High Yes 6.4
High Yes 8.4
Low Yes 0.9
High Yes 2.3
High Yes 4.5
High Yes 3.5
Medium Yes 2.3
Low Yes 1.9
High Yes 10.4
High Yes 6.6
High Yes 4.1
High Yes 2.7
High Yes 4
High Yes 2.4
92.0 10 Productivity (TC/Hour)
Hour
Testing progress Round 1
Source code version: V1.00

2023/4/13

Testing progress management: Round 1


1 Functions
1 5.2. User authentication
2 5.2. Common functions
3 5.3. First inspection
4 5.4. Second inspection
5 5.5.2. Parcel search
6 5.5.3. Data Extraction
7 5.5.4. Data summarization
8 5.5.5. Chute setting
9 5.5.6. Power management
Round 1 10 5.5.7. aaa Management
11 5.5.8. bbb Management
12 5.5.9. User management
13 5.5.10. Risk country
14 5.5.11. System status display
15 5.5.12. Log management
16 5.5.13. Cron-job
17 6. Show X-ray image
18 7. Combination
19 8. Non-functional (performance)
Total TC
Total % TC
Bug management: Round 1
2
1 5.2. User authentication
2 5.2. Common functions
3 5.3. First inspection
4 5.4. Second inspection
5 5.5.2. Parcel search
6 5.5.3. Data Extraction
7 5.5.4. Data summarization
Round 1
8 5.5.5. Chute setting
9 5.5.6. Power management
10 5.5.7. aaa Management
11 5.5.8. bbb Management
12 5.5.9. User management
13 5.5.10. Risk country
14 5.5.11. System status display
15 5.5.12. Log management
16 5.5.13. Cron-job
17 6. Show X-ray image
18 7. Combination
19 8. Non-functional (performance)
Total bugs

Improvement management: Round 1


2
1 5.2. User authentication
2 5.2. Common functions
3 5.3. First inspection
4 5.4. Second inspection
5 5.5.2. Parcel search
6 5.5.3. Data Extraction
7 5.5.4. Data summarization
Round 1
8 5.5.5. Chute setting
9 5.5.6. Power management
10 5.5.7. aaa Management
11 5.5.8. bbb Management
12 5.5.9. User management
13 5.5.10. Risk country
14 5.5.11. System status display
10 5.5.12. Log management
11 5.5.13. Cron-job
12 6. Show X-ray image
13 7. Combination
14 8. Non-functional (performance)
Total improvement points

Un-test test cases: 55

2022/03/07: 0 bug

2022/03/08: 0 bug

2022/03/09: 0 bug

2022/03/10: 0 bug
Number of TC Completed TC Un-tested TC
22 22
20 20
69 69
125 125
80 80
64 64
84 84
9 9
23 21 2
45 45
35 35
23 23
19 19
104 72 32
66 30 36
41 41 `1`
27 27
40 39 1
24 24
920 849 71
92% 8%

Number of bugs Fixed bugs Confirm by


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0

Number of improvement Fixed improvements


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0
7 8 9
Mon Tue Wed

Status Assigned to
Done A-san 15
Done B-san 18
Done 25
Done
Done 35 34
Done 23 39
Done 67
Done
Done 14
Done 32 13
Done
Done
Done
Done
Done
Done 41
Done 27
Done
Done
68 130 185
14% 20%

Status Remark
0 0 0

Status Remark
0 0 0
2022-Mar
10 11 12 13 14 15 16 17 18 19 20 21
Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon

7
2
44
75 50
11
2
17
9
6 1

35
23
19
72
30

25 14
24
107 152 55 152 0 0 0 0 0
12% 17% 6% 17% 0% 0% 0% 0%
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
22 23 24 25 26 27 28 29 30 31
Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu

0 0 0 0 0 0 0 0
0% 0% 0% 0% 0% 0% 0%
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
2023/4/13
#

MC

9
10

11

12
Task Effort
(hour)
Software installation (Web server) for MC 8
Integration testing (Round 1) for MC
5.2. User authentication 2.2
5.2. Common functions 2
5.3. First inspection 6.9
5.4. Second inspection 12.5
5.5.2. Parcel search 8
5.5.3. Data Extraction 6.4
5.5.4. Data summarization 8.4
5.5.5. Chute setting 0.9
5.5.6. Power management 2.3
5.5.7. EAD Management 4.5
5.5.8. OCR Management 3.5
5.5.9. User management 2.3
5.5.10. Risk country 1.9
5.5.11. System status display 10.4
5.5.12. Log management 6.6
5.5.13. Cron-job 4.1
6. Show X-ray image 2.7
7. Combination 4
8. Non-functional 2.4
Performance testing for MC 8
Confirm bugs (Round 1) for MC 10
Integration testing (Round 2) for MC 20
T.B.D base on result of round 1
Confirm bugs (Round 2) for MC 5
Total 281.7
35
PiC Remark 7 8 9 10 11 12
Mon Tue Wed Thu Fri Sat

(Hours)
(Day )
Not include Saturday and Sunday
2022/03
13 14 15 16 17 18 19 20 21 22 23 24
Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu

Author:
set up to test power on
after 3 day off and 5 days
off
Author:
Prepare data
# Category Risk
1 Environment HW installation is delay
+ Web server have not finished installation yet
+ Inspection terminal is not available ()
2 Environment Testing time is the same time with customer trial. It may make
to reduce testing productivity and delay schedule

3 Environment I/F between ;';';''; has problem

4 Requirement Change requirement while testing


Possibility Mitigation plan Contigency plan
High - Re-schedule testing
- Inform to bbb about impactation
- vvv discuss together to take direction
High - Select test item which not related - Select test cases following priority if
to hardware when customer use necessary
them

Low - Project team will support to solve problem


-bbb-san will hold meeting to discuss between
TSDV and TDSL if necessary
Low nnn will evaluate and avoid
requirement change at that time
Remark

You might also like