1 / 7

STS Test – BT & FT

STS Test – BT & FT. Siwert Streiffert. About the next slide. The following process chart is fetched from a presentation of the AP Platform Development Process, describing what was called ”the Micro process” (as opposed to ”the Macro Process”).

braden
Download Presentation

STS Test – BT & FT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. STS Test – BT & FT Siwert Streiffert

  2. About the next slide... • The following process chart is fetched from a presentation of the AP Platform Development Process, describing what was called ”the Micro process” (as opposed to ”the Macro Process”). • The original process chart is based on a strictly sequential (non-iterative) process. Does not really fit AZA/DJ way of working.

  3. Design increment testing (BT + FT) Assignment specification Design base Detailed Increment Planning and Negotiation Brainstorm Prototype BT strategy FT specification (Req based) Rejected 1/3 Design presentation Accepted Design andinspection Implementationand inspection BT design andinspection BT implementationand execution FT Design Local integration FT instruction Early delivery Release to System Integration The Integration Organization Function Test execution and reporting New testbed To System Test

  4. STS Basic/Component Test • BT strategy based on Software Quality Rank (SQR) • ”based on” since several key concepts are used, such as; code review, code coverage, memory leak detection, code complexity analysis. • Not quite level 3, since BT automation support is missing. • No documented BT process description exists. • Automated BT has been found to have too high cost/benefit ratio. Instead go for automated FT.

  5. STS Function Test • Documented FT process description exists (link to V) • FT runs in simulated environment (PAP) and target environment (APG40) with focus on the latter. • STPs (APG40&CP HW&SW) supplied by ETE in Linköping • Regression tests are maintained in an ordinary document (MS Word). A handful are automated via Winfiol. Still a lot of manual testing.

  6. STS FT (cont’d) • History of Plans to Automate FT : • In-house framework: FT-driver (java based). Never finished due to new directives... • PM&T (group function) suggestion: TTCN3 (C++ based framework). Test case development was given a ”go” but then... • APZ I&V directive: ATH (Tcl/Expect based framework). AZA/DJ has just started to look at that one... At the end of the day, the only implemented automated FT test cases are the ones where we had a framework to start with; Winfiol.

More Related