Joint Testware Development (JTD) ™

1. Joint Testware Development (JTD) ™ Dennis Janssen CMG TestFrame™ Research Centre dennis.janssen@cmg.nl

2. Agenda • Introduction • Hypothesis • What is JTD ™ ? • The Approach to JTD • JTD and Verification • Hypothesis re-visited • Summary • Questions?

3. Introduction • Test Manager & Test Consultant within CMG Finance • Experience: • Test Analysis • Test Management • Test Consultancy • QA Auditor • QA Manager.

4. Hypothesis Structured testing without correct, complete and up-to-date documentation is NOT possible!

5. But how about... • Legacy systems • Systems with no up-to-date documentation • Newly built systems of which the documentation isn’t ready….. yet • Testing the documentation itself!

6. Testing without documentation • Traditional, formal testing techniques are not usable • Structured testing is still necessary! • A solution: Joint Testware Development (JTD) ™

7. Joint Testware Development (JTD) ™ • JTD = A technique for structured test development without (complete) documentation • JTD= An alternative test technique, even if documentation is available (different coverage) • JTD<> Just talk to the end-users and write down what they say • Based on knowledge of experts instead of documentation

8. The Approach to JTD • Specify test products that are to be delivered • Put together the participants of a JTD workshop, based on the product that has to be delivered • Preparation by participants of the workshop • Perform workshop • Deliver an approved test product

9. Define products Products to be developed and documented with JTD: • Acceptance criteria • Risk test object • Priorities of test aspects • Description of test environment • Clusters • Test conditions • Test scenario’s & “test soaps” P1 Workshops P2 P3

10. Participants JTD Workshop • A JTD team can be different from workshop to workshop • Important qualities of participants • Experts on specific matters • Able to communicate • Participants in a workshop are authorized to make decisions for the group(s) they represent

11. Participants JTD Workshop Always present: • Moderator • Writer • Testers Depends on the product, for example: • End users • Developers • Maintenance • Quality Assurance/ EDP Audit • WHO EVER IS NEEDED!

12. Preparation to a JTD Workshop • Timely notification of participants • Presentation • Rules for a JTD workshop • Distribution of available documentation • Clear assignments for participants • Monitor preparation! • No preparation = No JTD-workshop

13. Execution of JTD workshop • Group process, synergy • Structured, led by a moderator • Every participant equal rights and responsibilities • Time boxed • Document results • Use of other test techniques in a JTD workshop is possible!

14. Delivery of test products • Always deliver a product • Testproduct is approved by the group • Product is documented, some details are filled in after JTD workshop

15. Critical factors for success • Defining tangible test products • Right selection of participants • Participants have authority to make decisions for the people they represent • Thorough preparation

16. JTD workshop will fail if... • Not enough preparation by participants • Not enough time for preparation • No authority to make decisions • Bad selection of participants • No management support (experts not available) • No clear goal • No documentation of results • No product defined

17. JTD and verification leads to JTD-workshop Rework Testcondities Compare with Documentation

18. JTD and verification • Compare JTD test products with delivered documentation • Discrepancies are noticed as soon as possible • Both “are we building the right system” and “are we building the system right” • Same procedures as with developing JTD products for dynamic testing • Test products are re-usable

19. Hypothesis, re-visited Structured testing without correct, complete and up-to-date documentation IS possible with JTD!

20. Summary • No documentation needed, but still a way to structured testing • JTD is an alternative test technique (not only when documentation is not available) • Develop products during workshops • Some hard demands for success! • Verification AND dynamic testing are supported