70 likes | 82 Views
1. TTCN-3 CONFORMANCE TEST SUITE STF 521 STATUS REPORT FOR MTS#71 MEETING. Andras Kovacs / BroadBit Tomas Urban / Elvior. 2. Contents. Session plan Current status Issues reported as CRs Conclusion. 3. Session plan. 4. Current status (1/2).
E N D
1 TTCN-3 CONFORMANCE TEST SUITE STF 521 STATUS REPORT FOR MTS#71 MEETING Andras Kovacs / BroadBit Tomas Urban / Elvior
2 Contents • Session plan • Current status • Issues reported as CRs • Conclusion
3 Session plan
4 Current status (1/2) • The planned test cases have been all completed and validated • Time spent on the following: • New test case development (extending ATS from STF487) • Coverage of differences between TTCN-3 ed. 4.7.1 and ed. 4.8.1. All changed or new clauses are being covered. • Taking ‘on-hold’ test cases from STF487 into use, based on the resolution of CRs raised by the preceding STF. • Validation and documentation • Validation with two independent TTCN-3 tools (TTWorkbench + Testcast). Still waiting feedback from Spirent experts. • Creation of deliverable documents.
5 Current status (2/2) • ATS is being validated with 2 tools: • TTworkbench: compile-time and execution. • TestCast: compile-time and execution. • All changes between the 2015 and 2016 editions of the TTCN-3 standard have been covered; tool vendors may validate their implementation of the latest features. • STF521 will be finished by end of June; feedback from any tool vendor is welcome till then. The deliverables and ATS shall be updated according to possibly received feedback.
6 Handling reported CRs • 20 CRs were written by STF521 (about 50%-50% for the core language part and XML part) • All of the CRs raised by preceding STF have been resolved, we checked through the on-hold test cases, and added some into the ATS.
7 Conclusion • STF521 work is progressing on track • STF521 will be finished by end of June. • Draft deliverable is available for review in MTS#71 contributions • There is a dialog with tool vendors regarding the analysis of observed errors - reporting till end of June is possible • Special thanks to Elvior and Spirent for the active tool support, which makes the continuous validation of results possible.