Software Testing Techniques: A Comprehensive Guide, Study notes of Software Project Management

Download Software Testing Techniques: A Comprehensive Guide and more Study notes Software Project Management in PDF only on Docsity!

Specification Based testing

• Also known as black box or input/output testing technique.
• No Knowledge about how system works.
• Tester is concentrating on what the software does, not how it does it.
• They are based on model of some aspect of specification.

Experience Based Testing technique

• People knowledge, skills and background as prime contributor to test conditions and test cases.
• Due to previous experience with similar systems, they may have insights into what could go wrong.

Equivalence Partitioning

• Divide a set of test conditions into groups or sets that can be considered the same.
• It is also called as equivalence classes.
• We test one condition from each partition.
• If one condition works then assume that all condition work.
• If one condition does not work, then we assume that none of them work.

Equivalence Partitioning

• If you are testing for an input box accepting numbers from 1 to 1000 then there is no use in writing thousand test cases for all 1000 valid input numbers plus other test cases for invalid data.

Equivalence Partitioning

• Using equivalence partitioning method above test cases can be divided into three sets of input data called as classes.

• A saving account in a bank earns different interest rates depending upon the balance.
• E.g. If balance range 0$ to 100$ - > 3% interest rate
• Balance over 100% to 1000% - 5%
• Over 1000% - 7% interest rate

• Invalid Partition- - 0.01$
• Valid (3% interest) – 0.00$ to 100.00$
• Valid(5% interest) – 100.01$ to 999.99$
• Valid(7% interest) – 1000$

Boundary Value Analysis

• Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

Boundary Value Analysis

• It is based on testing at the boundaries between partitions.
• Enhancement of equivalence partitioning.
• E.g. consider a printer that has an input option of the number of copies to be made from 1 to 99
• Invalid - 0
• Valid - 1 to 99
• Invalid - 100

Boundary Value Analysis

Test cases for input box accepting numbers between 1 and 1000 using Boundary value analysis: 1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case. 2 ) Test data with values just below the extreme edges of input domains i.e. values 0 and 999.

Decision Table Testing

• Decision Table Testing is a good way to deal with a combination of inputs, which produce different results.
• It helps reduce test effort in verifying each and every combinations of test data, at the same time ensuring complete coverage.

Decision Table Testing Example

• Rule 1: When destination for both Fly From & Fly To are not set the Flight Icon is disabled. In the decision table, we register values False for Fly From & Fly To and the outcome would be False, which is Flights Button will be disabled. Likewise, you can decide different outcome for different situation.

Decision Table Testing Example