Testing : Testing And Automated Testing

Testing of the entire system will be performed to verify that all parts and counterparts are functional. This is the testing that is made prior to release. Tests performed in this stage verify for the following:

Test Plan: The software is tested using two levels of testing viz. black box testing and white box testing. White box testing could be carried out in three different phases viz. unit testing system/integration testing and validation testing. • Unit Testing: Unit testing, also known as Module Testing, focuses verification efforts on the module. The module is tested separately and this is carried out at the programming stage itself.Unit Test comprises of the set of tests performed by an individual programmer before integration of the unit into the system. Unit test focuses on the smallest unit of software design- the software component or module. Using component level design, important control paths are tested to uncover errors within the boundary of the module. Unit test is white box oriented and the step can be conducted in parallel for

System testing will help identify if normal or incorrect actions in the program are working correctly because every line of the program code should be able to execute test errors messages.

It plays a crucial role in the development of an application. Testing should be done to validate the product whether it met all the requirements and to check whether it is being developed according to design or not.

Rather than showing users a rough draft and asking, "Do you understand this?", usability testing involves watching people trying to use something for its intended purpose. For example, when testing instructions for assembling a toy, the test subjects should be given the instructions and a box of parts and, rather than being asked to comment on the parts and materials, they are asked to put the toy together. Instruction phrasing, illustration quality, and the toy's design all affect the assembly process.

The developers who worked on the application may change work or else choose to bring projects in-house to have it developed and /or maintained by our own staff as automated test facilitate code refactoring. With the automated test on hand developer can change the code and run the test to easily and find out that the changes made have impacted the system or not.

Testing is a procedure of executing a project with the goal of finding a mistake.

Unit testing is a software development process where the smallest testable parts of an application are independently tested in isolation for proper operation. It is often automated and can be done manually. This form of testing is a component of Extreme Programming, where it takes a meticulous approach towards software development by means of continual and revision testing. The unit tests should be calls to these routines with different input parameters. In addition, unit testing involves only the characteristics that are vital to unit performance under test, which encourages the developers to manipulate the source code without immediate concerns about how such changes would affect the functioning of the program as a whole. Once all units in a program has been found to be working efficiently, larger components of the program can be evaluated via integration testing.

Abstract—Although Concolic testing is increasingly being explored as a viable software verification technique, its adoption in mainstream software development and testing in the industry is not yet extensive. In this paper, we discuss challenges to widespread adoption of Concolic testing in an industrial setting and highlight further opportunities where Concolic testing can find renewed applicability.

There are many metrics and tools used in the software industry that attempt to describe the effectiveness, usefulness and completeness of software tests. A common metric of “test coverage”, also known as “code coverage”, is used to quantify how much code of a particular program that tests are covering. Test coverage however does not require that the tests are of high quality, and does not require the tests to take into account how a program may change or evolve over time. Because of this, a program with a quantitatively high test coverage is not necessarily a program that has effective tests that will spot changes, or “mutations”, in the code. Code is constantly being modified, added, and removed during a normal software development process. It is important for programs to have tests that are effective throughout the development process.

Manual testing is better than automated testing. All the above mentioned process models are widely used under manual testing, in which human beings perform this sort of testing. Automated testing is done by the computer which reduces the man power but not matter how fast a computer works it never thinks as human being ("Which is better," 2013). Even after a product is developed by using automation testing it cannot be completed without manual testing. A software test engineer must check the result of the automated test manually. Automated test stops even for simple unexpected pop-up dialogue which should be cleared by manual testing. Manual testing requires human judgement in which a human being executes the test cases in order to obtain the desired output. By using this one can find more bugs and fix them where automated testing does not find as many as manual testing. Layout, usability issues and trivial bugs can be identified by manual testing where automated testing cannot ("Which is better," 2013).

Functional testing is usually performed by creating inputs as per functional or design specifications given, executing the test cases and then validating the outputs against the expected outputs which are initially determined according to the specifications (Walker, ElshennawY, Gupta, & Vaughn, 2012). Functional testing is a type of Black box testing. Functional testing can be automated for most of the cases by which the user intervention can be minimized. According to Stackpole & Hanrion (2008), “Functionality tests cover the ability of the system or application to initialize, communicate with its components and support services, and interact with users.” By performing functional tests on web applications, users can identify bad links on web pages and unreachable pages (Casteleyn, Daniel, Dolog, & Matera, 2009).

There are many existing tools like Quality Center which is licensed by HP. All the stages are designed and implemented manually from requirement analysis, designing test plan, developing test scenarios, writing test cases, executing the test cases, defect reporting etc. The problems with manual testing are time consuming and non-reusable and no scripting facility, manual effort required and few errors are uncovered [1]. Manual Testing is preferred to review the application requirements, and to create the High Level design Documents and Low level design Documents [3].

In data flow testing, the program graph for the software component under test is further analyzed. Data flow

“The totality of features and characteristics of the entity that bear on its ability to meet stated and implied needs”