SilvioCacace? from Ordina has written an article on a structured testing approach when you are doing a SMART project. I'll try to summarize it in English.
SMART is:
* Object Oriented, UML, iterative and incremental approach, team workshops for customer, developer, user and tester to figure out the specifications, teams are 'multi-disciplined' (correct English?)
Smart and Testing
* every increment should be tested
* all increments together should be tested in an Integration Test
* the traditional system tests and acceptance tests are joined togetther (as in XP), called System acceptance test (SAT?)
* Within the SAT there is a System integration test (SIT?), to test the integration of the several increments. There is a figure on this, can that be put on a Wiki?
I guess Silvio was influenced by the structured test approach TMAP, since he defines 3 phases in SmartTesting: Preparation, Execution and Completion. And I think the activities as described below, are quite formal. It looks as if it was written before he actually did a SMART project, it is quite theoretical (as if it had to fit in some kind of ISO or CMM procedure / assessment). I wonder if it's necessary to be so thorough?
System Acceptance Test
Activities during SAT Preparation: intake testbasis, decide on test strategy, writing test plan, writing test scenario´s, developing test cases, creating the 'starting point' of testing (where in the app I guess), setting up the test tool(s), setting up a Test Log (I'm not sure what is meant with that)
Activities during SAT Execution: executing test cases, register bugs, re-test the bugs, regression test, writing test log.
Activities during SAT Completion: write testreport, saving testware, write test log
Process: Writing test scenarios for Functional and Non-Functional (Security and Usability ) Requirements, based on the UML diagrams and Use Cases. Write a flowchart for each use case, including actions, decisions and validations. Test cases for Non-functional reqs are devloped through error-guessing by the user. (??? Why not exploratory??), pre-conditions for test execution.
System Integration Test
The flowcharts from the SAT were written for each use case. In the SIT all flowcharts are combined together, so the several use cases are tested in close relationship with eachother. These are the test scenarios for the SIT.
Back to AgileTesting
