Integration & System Testing

Talveer Chaira Integration & System Testing

G53QAT

Integration & System Testing

Monday 26th November 2009


G53QAT

Contents

Introduction Integration Integration Testing Process Test Data Different Types of Integration Testing Top-down Bottom-Up System Testing Testing Again Conclusion References


G53QAT

Introduction

Integration and system testing is a type of software testing

very strict set of rules and guidelines in Testing

There is a testing team who just focus on the testing aspect

software testing each level build on from the previous level


G53QAT

Integration

Integration testing comes before system testing and after the unit testing in SDLC

“Integration testing is a software development process which program units are combined

and tested as groups in multiple ways.” 1


G53QAT

Integration Testing Process

Integration testing stage there are three things that

are created;

• Test Plan• Test Case• Test Data


G53QAT

Test Plan

What a test plan Includes;

• a strategy to use when testing the integrated modules and how the tests will be conducted.

• What will be tested for example software features.• What is the time scale and time management.

• Responsibilities.• Testing pass and fail condition.

• Risk involved• Approval from all important people involved.


G53QAT

Test Case

Test cases is created to check the output, of the integrated modules are producing the expected output.

Below is a simple test case;


G53QAT

Test Data

“Test Data is data which has been

specifically identified for use in

tests” 2

“Test data may be recorded for re-use, or used once and then forgotten.” 2


G53QAT

Different Types of Integration Testing

Big Bang

“The way this integration testing type works is, most or all of the modules are integrated together to form nearly a complete

system.”

Advantages• Good for small Businesses

Disadvantages• Time delay• Hard to identify errors & bugs• All testing has not been done


G53QAT

Top-down

Top-Down“highest level components are tested first and then step by

step start working downwards.”

Advantages• good prototype • easy to maintain the code • better control in terms of errors

Disadvantages• hard to test the lower level components


G53QAT

Bottom-Up

Bottom-Up“This is the opposite to top-down”

Advantages• easy to maintain the code

Disadvantages• Prototype• Errors Later on


G53QAT

System Testing

“System testing is simply testing the

system as a whole”

“In the system testing process the system will be checked for

errors and also to see if the system does

what was intended.”


G53QAT

Testing Again

Various tests that need to be conducted again;

-Test Plan -Test Case -Test Data

Types of System Testing;• Usability testing

• GUI software testing• Security testing

• Accessibility• Reliability testing


G53QAT

Conclusion

Integration and System Testing can;

• Minimise Errors• Help Keep Within Budget

• Problems are easily identified


G53QAT

References

1. What is Integration testing, TechTarget [online], Available at: http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html [Accessed 20th November 2009]

2. Test Data, wikipedia [online], Available at: http://en.wikipedia.org/wiki/Test_data [Accessed 20th November 2009]

http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html

http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html

http://en.wikipedia.org/wiki/Test_data


G53QAT

The End

Any Questions ?

Documents

Integration & System Testing