Week9 - Monday, March 2 1 Overview Last Class Testing...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
1 1 Monday, March 2 © Susan Elliott Sim, 2009 Week 9, Slide 2 Inf111/CSE121 Overview • Last Class – Testing Review • This Class – Testing – JUnit • Next Class – Testing
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 © Susan Elliott Sim, 2009 Week 9, Slide 3 Inf111/CSE121 Testing Objectives • Goal of testing is to make the software misbehave – Failures tell you a lot more than successes • Your reward is finding a bug, even if it’s your own code – No prizes for test cases that pass • Testing can only tell you about the presence of defects – Need to use proofs and other checks to show correctness © Susan Elliott Sim, 2009 Week 9, Slide 4 Inf111/CSE121 The Tester’s Role on Agile Projects Testers in their traditional role Tester role in an agile project A separate QA group Tests are derived from detailed requirements and specifications QA may or may not participate in planning sessions, but is not usually informed about design considerations until after they have been finalized Is part of the team and attends all team sessions Is an integral part of the planning game Practices pair testing, i.e. collaborates with the developers to get good tests http://www.ucalgary.ca/~ageras/wshop/abstracts/2003/role-agile-tester.htm
Background image of page 2
3 © Susan Elliott Sim, 2009 Week 9, Slide 5 Inf111/CSE121 Test Planning • Quality Criteria – What are you testing for? • Techniques – How are you going to test? • Sufficiency Criteria – How many test cases are enough? © Susan Elliott Sim, 2009 Week 9, Slide 6 Inf111/CSE121 Quality Factors Will I be able to… …use it on another machine? …reuse some of the software? …interface it with another system? Product Transition •Portability •Reusability •Interoperability Can I fix it? Can I test it? Can I change it? Product Revision •Maintainability •Testability •Flexibility Does it do what I want? Does it do it accurately all of the time? Will it run my hardware as well as it can? Is it secure? Can I run it? Product Operation •Correctness •Reliability •Efficiency •Integrity •Usability
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 © Susan Elliott Sim, 2009 Week 9, Slide 7 Inf111/CSE121 Quality Assurance Activities • Verification – Check product against specification – Building the system right • Validation – Check product against world (stakeholder expectations) – Building the right system • van Vliet considers all quality assurance activities as testing © Susan Elliott Sim, 2009 Week 9, Slide 8 Inf111/CSE121 What are good tests? • Depends on the quality factor – Some quality factors are hard to test for and need to be built in • Most basic are correctness and reliability – Others are more specialized • Need some for success scenarios – Singly and in combination • Need many for extensions, alternatives, and exceptions – Majority of the work (thinking and typing)
Background image of page 4
5 © Susan Elliott Sim, 2009 Week 9, Slide 9 Inf111/CSE121 Automated Testing • Idea: Testing is repetitive. Get a computer to do the
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/27/2010 for the course CSCI 561 at USC.

Page1 / 19

Week9 - Monday, March 2 1 Overview Last Class Testing...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online