07-08-2012, 04:41 PM
System testing
SYSTEM TESTING.doc (Size: 35 KB / Downloads: 32)
SYSTEM TESTING
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. System testing tests not only the design, but also the behaviour and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specifications.
TESTING STRATEGIES
A test strategy is an outline that describes the testing approach of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment.
Test strategies describes how the product risks of the stakeholders are mitigated at the test-level, which types of test are to be performed, and which entry and exit criteria apply. They are created based on development design documents. System design documents are primarily used and occasionally, conceptual design documents may be referred to. Design documents describe the functionality of the software to be enabled in the upcoming release. For every stage of development design, a corresponding test strategy should be created to test the new feature sets.
CODE TESTING
Specification testing is done to check if the program does what it should do and how it should behave under various conditions or combinations and submitted for processing in the system and it is checked if any over laps occurs during the processing. This strategy examines the logic of the program .Here only syntax of the code is tested. In the testing syntax errors are corrected. To ensure that the code is perfect we perform unit testing and system testing.
UNIT TESTING
Unit testing, also known as component testing , refers to tests that verify the functionality of a specific section of code, usually at the function level. It is the first level of testing. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.
These types of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other.
SYSTEM TESTING
System testing tests a completely integrated system to verify that it meets its requirements .The next level of testing is system testing. System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. System testing tests not only the design, but also the behaviour and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specifications.