Article for last Tuesday

1
Article for last Tuesday

• Enhancing Software Testing by Judicious Use of
  Code Coverage Information

2
Would you like to work for this company? Why or
why not?
3
Was there any group that did not use the new
technology effectively?
4
Was there a better way to encourage technology
transfer?
5
What was their approach to testing and was it
great?
6
A set of sophisticated mocks to simulate
themessaging infrastructure of the underlying
enterprise service bus.
7
A user interface 2 to run all automated tests
independently from the development environment.
8
Software Testing

• Structural testing revisited

9
Other test documents

• test-case specification
• inputs, outputs, procedures
• test-procedure specification
• test log
• test-incident report
• test-summary report

10
Other Testing Strategies

• Performance Testing
• Stress Testing
• Worst Case Testing
• Random Testing

11
Team Discussion - strategies

• Do any of the list of testing strategies apply to
  your team project?

12
Testing Phases

• module/unit testing
• integration testing
• system testing
• validation/acceptance testing
• regression testing

13
Integration Testing

• top-down
• code and test the top module first, using stubs
  to represent the uncoded modules
• bottom-up
• code and test the bottom modules first, using
  simple drivers to execute the modules
• big-bang
• doing everything at once

14
TTYP - Team - integration

• How should your team do the integration testing
  of your project?

15
Other Testing Strategies

• Performance Testing
• Stress Testing
• Worst Case Testing
• Random Testing

16
partial contents of aTest Plan (IEEE Standard)

• identifier
• introduction
• test items (what is to be tested)
• features
• to be tested
• not to be tested
• methodology

• pass/fail criteria
• suspension criteria
• deliverables
• responsibilities
• schedule
• contingency plans
• approvals

17
Test Plan part 1

• Identifier
• A unique name, version number
• Introduction
• What is project, etc
• test items (what is to be tested)
• Specific identifier of items

18
Test Plan - part 2

• Features
• to be tested
• What functionality, capabilities
• not to be tested
• Is there anything to be excluded?
• Methodology
• Overview of approach

19
Test Plan part 3

• Pass/fail criteria
• When is testing through, positively or not
• Suspension criteria
• When is testing halted for more development,
  debugging work?
• Deliverables
• What reports, etc are delivered

20
Test Plan part 4

• Responsibilities
• Who is responsible for what tasks
• Schedule
• contingency plans
• What if plans can not be followed
• Approvals
• Who approves what

21
Other test documents

• test-case specification
• inputs, outputs, procedures
• test-procedure specification
• test log
• test-incident report
• test-summary report

22
Future

• Thurs, Nov 8 - Exam preview
• Tues, Nov 13 - Exam