You are on page 1of 2

*software testing act should start asap in the sdlc

*faults found by users are due to poor software and poor testing

*standad related to testing


- IEEE829
- BS7925-1
- BS7925-2

*component test standard


- IEEE 829
- IEEE 610
- BS7925-1

*intergration strategy
- big-bang
- bottom-up
- top-down

*black box design technique


- statement testing
- error-guessing
- usability testing
(!= equivalence partitioning)

*static test
- coverage analysis
- usability assessment
- installation test
(!= code inspection)

*non-functional testing methods


- usability testing
- performance testing
(!= system tesing)

*correct form of logic coverage


- statement coverage
- condition coverage
- path coverage
(!= pole covergae)

*quality characteristic listed in ISO 9126 standard


- functionality
- usability
- maintainability
(!= supportability)

*acceptance test cases based on requirements

*component test technique


- statement testing
- branch testing

*statement coverage will check


- unused branches
- dead code
- unused statement
(!= missing statements)
*when to stop testing
- when the test completion criteria have been set

*coverage measurement
- a partial measure of test throughness

*incident logging system


- valuable source of project information during testing if it contains all
incidents

*testware (test cases, test dataset)


- needs configuration management just like requirements, design and code

*test design technique is


- a process for selecting test cases

*black box tester


- should understand a functional specification or requirements document
- highly motivated to find faults
- creative to find the system's weaknesses
(!= understand the source code)

*reporting faults to dev, testers should be


- polite, constructive, helpful
- insist that a bug is not a 'feature'
- diplomatic, sensitive to the way they may react to criticism

*order of testing = most important tests first

*fault discovered later is more expensive to fix, because the fault has been built
into more documentation, code, tests

*increase quality of the software, by better development methods, will affect te


time needed for testing (the test phases) by ---> reducing test time

*true
- performance testing can be done during unit testing as well as during the testing
of whole system
- the acceptance test does not necessarily include a regression test
- test environments should be as similar to production environments as possible

* false
- verification activities should not involve testers (reviews, inspections)

You might also like