Considerations about ATS related issues Group Name TST

Considerations about ATS related issues Group Name: TST WG Source: Keebum Kim, TTA, keebum. kim@tta. or. kr Subhash Gajare, Spirent, Subhash. Gajare@spirent. com Meeting Date: TST #32

Bug report and tracking • Currently several companies are working on the ATS TTCN-3 codes. • To not duplicate the efforts, the bug report and tracking is getting important. • Ways to report and track Bugs, – Manually by using e-mail. – Using issue submit function in gitlab. – Setting up a professional open source tool. (E. g. Bugzilla) © 2017 one. M 2 M Partners TST-2017 -0271 2

Bugs to report • Based on ATS branch Release 1, commit 656 c 88 aff 9 d 4198 fda 362 dbea 0 d 67 be 4 b 502507 f, 16 th Oct 2017 – Does not delete AE resource after end of test. • Test case it self it not a problem but the test case those execute after cause conflict errors. • TC_CSE_REG_CRE_002 – Conflict error occurs by double creating AE. • TC_CSE_DMR_RET_013_AE, TC_CSE_DMR_RET_015_AE, TC_CSE_DMR_RET_016_AE, TC_CSE_DMR_RET_017_AE, TC_CSE_DMR_RET_018_AE_LBL, TC_CSE_DMR_RET_019_AE_LBL_AT, TC_CSE_DMR_UPD_017_AE_LBL, TC_CSE_DMR_UPD_017_AE_ACPI, TC_CSE_DMR_UPD_017_AE_APN, TC_CSE_DMR_UPD_017_AE_POA, TC_CSE_DMR_UPD_017_AE_OR, TC_CSE_DMR_UPD_018_AE_ET, TC_CSE_DMR_UPD_018_AE_RR • How could we report these bugs? In which format? And how could we know these bugs are solved in which commit? © 2017 one. M 2 M Partners TST-2017 -0271 3

ATS TTCN-3 code review system • To prevent bugs, review system is necessary. • Some bugs existing in current ATS TTCN-3 codes, could be possible to prevent during git commit. • Ways to apply review system – Use normal git functions with manual managing – Setting up professional open source tool. (E. g. gerrit) © 2017 one. M 2 M Partners TST-2017 -0271 4

Gerrit • Gerrit provides web based code review and repository management for the Git version control system. • Website: https: //www. gerritcodereview. com/ • Provides, – Discuss code – Manage and serve Git repositories • Navigate projects • Control access • Update branches © 2017 one. M 2 M Partners TST-2017 -0271 5

Version freezing policy • Before publishing the ATS TTCN-3 codes, to verify, it requires code freeze time period. • During the code freeze, only bug fixes could be allow to commit. – No more huge structure changes. – No new add or remove of test cases. – No critical changes in test cases. • If the codes changes frequently until the last day before publishing, it will be difficult to verify and to prevent side effects from the changes. © 2017 one. M 2 M Partners TST-2017 -0271 6

Grouping by Product Profile • From the experience of executing the ATS TTCN-3 test cases, it was difficult to know which test cases are included in the product profiles. • Perspective of certification testing, it is very important to know which test cases are mandatory to perform the testing. • Current grouping structure is also useful to perform function base testing. • To achieve both objectives, we propose to generate a second TTCN test case file only including the grouping structure based on product profiles and link the test cases from the original TTCN test case file. © 2017 one. M 2 M Partners TST-2017 -0271 7

Thank you