CHAPTER 5
SOFTWARE TESTING
5.1] Test Case
5.1.1] Test Procedure and Implementation:
Test Procedure:-
The software testing is the critical element of software quality assurance and represents the Ultimate review of the software design and coding. The main objective of testing is to find an error and to uncover the errors that are not yet discovered.
This increasing visibility of software as a system element and the attendant cost associated with a software failure and motivating forces for well planned, through testing. It is not unusual for a software development organization to expand between 30 to 40% of project effort on testing. In the extreme,
…show more content…
• To make sure that the system meets the user requirements during the operations.
• To cross check the when current input are fed into the system outputs are correct.
• To make sure that during the operation incorrect inputs and the outputs will be detected.
• In testing process the number of strategies have been used as mentioned below,
Unit Testing
Integration
…show more content…
Here we test the system function manner that can be reasonably expected by the customer, the system was tested against system requirement specification.
Black Box Testing: After performing validation test, the next phase is output test of the system, since no system code be useful if it does not produce the desired output in desired format. By considering the format of the report/output, output/report is generated or displayed and tested. Here output format is considered in two ways, one is on the screen and other is on printed form.
User Acceptance Testing:
User acceptance test of a system is the key factor for the success of the system. The system under consideration was listed for user acceptance by keeping constant touch with the perspective user of the system at the time of design, development and making change whenever required. This is done: - Input Screen Design Output Design.
5.1.2] Implementation
Project Name : - Pharmaceutical Distribution System.
Prepared Date :- 03-05-2016. Reviewed Date :-
This testing level will also occur during the early development of the application but not until each of one of the subsystem’s unit functions have been fully tested and are ready to be implemented. While all three subsystems, financial, appointments, and patient records may not be tested in tandem each should be able to have basic testing performed with the use of test cases for input. Once they have completed testing, we could then use the same or similar test cases for the integration level testing of all subsystems.
Because of complexity and the way it (project) is too long each team member is assigned a task, making code for each programmer not to be too long. Both unit and module testing are accomplished here by software developers. The computer language like C++, Java, Pascal, COBOL and other programming languages is used for coding. On receiving system design documents, the work is divided in modules and actual coding is started. Since, in this phase the code is produced so it is the main focus for the developer. This is the longest phase of the software development life
To make sure it is a fair test; the procedure is repeated a couple of
allows for a less error free environment. It also allows the Unit to see exactly where the
There are many different types of student response systems. The most common student response system includes a set of handheld devices, otherwise called the input device, software to develop the questions and collect the data, and a projection system. Input devices come in three basic types with a variety of shapes and sizes. The first type is an input device that merely sends the student’s response to the computer software which collects the data, with no feedback to the students. The second type is an input device that sends and receives information, to indicate if the question was responded to ...
Abstract— Software testing is very important element in various product accuracy. Software testing is set of activities conducted with the intent of finding errors in software. It also verifies and validate whether the program is working correctly with no bugs no not. There are basically three levels of testing- Unit, Integration and System. Unit testing referred to as testing in small whereas Integration and System testing are referred to as testing in large. Various testing techniques available for designing of test cases. This paper basically deals with various techniques available to design software testing test cases.
1.0 IntroductionIn this report I will be concentrating on the failure of software systems. To understand why software systems fail we need to understand what are software systems. Software systems are a type of information system. This is because a software system is basically a means for hardware to process information. Flynn’s definition of an information system is:"An information system provides procedures to record and make available information, concerning part of an organization, to assist organization-related activities."Humans have been processing information manually for thousands of years, but with the vast increase of demand for knowledge this century has meant that a new method of information processing has been needed. Software systems have provided a new means that is much faster and efficient.
This report will first examine the Testing Process Summary. This will include a definitive test plan which will identify the major functions of the systems software and hardware to be tested as well as the required system outcomes. Secondly, the installation process and training plan summary will be identified. For this portion of the writing, a Gantt chart will be used to identify the steps and related resources needed to implement the system. A narrative explanation that will discuss the impacts of time and conversion will be included. A description of the training plan will also be outlined. The third section of this writing will summarize the company documentation plan. This will include the identification and explanation of all forms of documentation used throughout the project. The chosen documentation for the technical and user sides of the system will be identified. Lastly, the company support and maintenance plan will be summarized. This plan will outline the chosen software, hardware and networks in regards to the responsibilities of each area. The related resources necessary to properly support and maintain the system will also be identified.
While developing a software many complex activities are required which in turn have dependencies along them. Large software projects require the involvement of programmers, documentation specialists, program managers, architects, database analysts, system analysts, , and trainers and last but not the least testers. Along with their independent responsibilities these persons are also responsible to maintain and keep a check on the software system quality as well.
to find out if it has change from the past. There are two models of
Mr I Langdon, “CE811-7-SP: DEVELOPMENT OF LARGE SOFTWARE SYSTEMS”, Soft-ware Testing lecture, Spring Semester’10, University of Essex, UK.
The SDLC is a problem-solving process which through a series of steps helps produce a new computer information system. Each step from system planning, system analysis, system design, system implementation and to system maintenance conducted in sequence should provide the answers to a problem or opportunity (Farah, 2006). An example may be a user which employs an order system may sense a problem with that system because customers may complain that orders are late or being lost. The SDLC through the steps previously mentioned would help correct and improve the system and operations of the order entry process (real life situation at KCI Medical Canada-Vancouver office). In this example, the system planning phase determines whether a new order entry process should be developed. The system analysis phase helps the analyst study the current system in place (order taken over the phone and input to an excel spreadsheet) and determines what shortcomings the new system must overcome (why are orders lost or delivery of product so late?) to ensure smooth operations within the order entry process. During the next stage, system design, the analyst specifies how the new system will operate. This is followed by the implementation phase where programs are acquired and tested to accommodate the new order entry process. Finally the system maintenance phase reviews the new order entry system to ensure smooth operations and modifications as needed.
With information and IT systems being critical in a company’s success and superior systems allowing more efficient business processes and the opportunity to gain a competitive advantage in the industry, companies and developers tend to test software thoroughly and rigorously; and spend more than 50% of their time and resources within the testing phase to ensure systems are “bug-free” and all requirements is in accord.
Software development follows a specific life cycle that starts with designing a solution to a problem and implementing it. Software testing is part of this software life cycle that involves verifying if each unit implemented meets the specifications of the design. Even with careful testing of hundreds or thousands of variables and code statements, users of software find bugs. “Software testing is arguably the least understood part of the development process” and is also a “time-consuming process that requires technical sophistication and proper planning” (Whittaker 71) It is important to comprehend this concept by understanding the different characteristics and aspects of software testing, and then to examine the techniques, procedures and tools used to apply this concept. This will enable the user to realize the problems faced by software testers and the importance of software testing.
Reliable, efficient, trustworthy and economically sound systems must be produced by software engineers. If good software engineering practices are not followed, this could lead to higher costs for testing the software, quality assurance (meeting standards) and long term maintenance.