7.

0 System Testing

7.1 Testing Stages

The proponents testing stages has two parts; these are unit testing and system testing.

Unit testing is a method by which individual units of source code are tested to determine if they are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. Unit tests are created by programmers or occasionally by white box testers.

Ideally, each test case is independent from the others: substitutes like method stubs, mock objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit tests are typically written and run by software developers to ensure that code meets its design and behaves as intended. Its implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation. [WIKI2011]

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.

As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the

hardware. System testing is a more limiting type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole. [WIKI2011]

In unit testing basic program modules are tested by the programmers who wrote the program, at this stage the proponents and the programmers usually take up their own test data or use a program that will generates test data. Second part is system testing, in system testing once the programmer and the proponents is confident that the system is working properly, it`s time to conduct test to the entire system. The purpose of this test is to see that the system is working properly. The nature of this test is quite different from unit testing. In unit testing the programmer is trying to see if the program makes specification; the assumption is that the specifications are correct, but in the system testing with user involved, not only are we testing the program but also we are testing our understanding of the whole system.

7.2 Testing Schedules Unit testing schedules was done after the whole program is developed. The proponents will test the program and fixed all the bugs and errors in which they thought would prevent the program from working properly. System testing schedule was done after the system is being presented to the client. User of the said system will use the program with the guidance of course of the developer of the system.
Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings (see white-box testing). Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. The tester is only aware of what the software is supposed to do, but not how i.e. when he enters a certain input, he gets a certain output; without being aware of how the output was produced in the first place
[1]

. Test cases are built around specifications and requirements, i.e., what the application is

supposed to do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the test object's internal structure.