Proper Testing Methodologies Computer Science Essay

Published:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Henceforth it is advisable to conduct proper tests and proper testing methodologies before the errors became the defects of the software.

8.1 Test Plan

The testing process is a process that to a great extent runs in parallel with other processes. The activity of testing begins early in the development.

Put it in a simple way, a good product will be work perfectly, doing the right thing at the right time. To do that, the software has to go through a series of tests before its final release. Error free software is extremely difficult to achieve. After all, nothing is perfect. Especially for software developed in a short time frame. But high quality can be achieved with a detailed test specification. All (or least most) of the test case will be listed, I will follow it step by step, item by item, to test all the necessary functions, data flows, limits, boundaries, and constraints of the software.

I want the product to be bug free. I also want to make sure that there are no defects in the product. So I will be spending large amount of the total software development time on the testing. Below is the description of the testing procedure and strategy. I will also be presenting the timing and scheduled of the tests to be carried out.

Conventional Testing is strategically similar to testing of OO systems, but it is tactically different. Because the conventional analysis and design models are similar in structure and content to resultant conventional program, "testing" begins with the review of these models. Once code has been generated, conventional testing begins "in the small" with functions testing. A series of tests are designed that exercise functions operations and examines if error exist when one function interacts with others. Finally, function based testing is used to uncover errors at software validation level.

So the software is tested at various levels by various testing techniques like black box, white box, Unit testing and Integration testing etc. Initially all the operations are tested separately while development. This is unit testing and as the developer does it, so it is white box testing. Once the operations are tested separately the leader of the phase integrates it with the other classes and he performs Integration cum Black box testing. And he gives remarks to the developer about any error.

After all at the end to test the software at software validation level I performed test case based testing. In which inherited test cases from the functions of the system developed in the Analysis phase in Dynamic Model.

System Test

Use Case Test

Subsystem Test

Delivered System

Designed & implementation model

Requirement model

Fig. 8.1 Testing Process

TEST STRATEGY

Unit testing-Module testing

In this testing individual components and modules are tested to ensure that they operate correctly. We had tested each and every module such as login, member details, project details and finally the generation of reports. For this we have checked the database for particular entry for validation.

Integrated testing

This testing is a systematic technique for constructing the program structure while at the same time conducting test to uncover errors associated with interfacing. All the modules testing in the unit testing are integrated and are tested for their interdependency.

Validation testing-alpha testing

Alpha testing is conducted at the developer's site by a customer. The customer which is here the employees of the COMPANY; test the system by entering live data. If any error occurs in the system they directly contact us. During this testing they have uncovered error such as the tab index properly was not set and the edit and deleting of the records has to be included.

Security testing

This testing is done to confirm that the software ALLOWS only authorized users to access and use system. There are two levels of security in this system. We have tested entering the user name and password for both the security levels to show them the information pertaining to their work only.

Human factor testing

The user can not do any thing if after submitting a transaction through a TERMINAL. THE screen goes blank while the data are being processed. They may not take the action the analyst wanted or expects, instead responding in unusual ways.

8.3 TEST METHODS

Stress Testing

Stress testing is to test the system for emergent properties such as performance and reliability. Performance tests have to be designed to ensure that the system can process its intended load. Here, we checked out the multi-user capability of our system.

Performance Testing

Performance testing is designed to test the runtime performance of the system within the context of the system. These tests were performed as module level as well as system level. Individual modules were tested for required performance.

In performance testing I counted the processing time and response from the server with respect to request.

Black-box Testing

We have tested functions of component to check the specification of all components. I selected input set to test the each component in the process I gave the different kinds of inputs to examine their output. I test software with sequences that have only a single value.

Interface Testing

Interface testing is integral part of Integration testing. Therefore I checked for the

Interface misuse

Interface misunderstanding

I examined the code to be tested and explicitly list each call to an external component. In the system, standards tests for GUIs have been performed. Which are as follows:

Testing the screen control for its position and size.

The position and related labels for all controls were checked.

Name of the form in system is given appropriately.

All functions were verified for correctness.

Validation for all inputs were done.

Each links were tested, whether it redirects the corresponding screen properly.

Pull down controls was verified for proper functionality.

Whether the non-editable text control is disabling and it was also verified that it doesn't exceed the maximum allowed length.

Whether the system prompts the user with appropriate message as and when invalid information is entered.

All required fields aren't left blank

8.4 TEST CASE DESIGN

Test cases are designed to check system functionality to ensure Software quality. Here we have designed Test cases, which are directly derived from the system scenarios from the analysis phase. These scenarios are developed to identify events and actions in the system. They assist here for test case development because they are sequence of interaction between system and user. For sample we have given few test cases below:

TEST CASE ID : TC001

NAME : Check Focus

Purpose

Check Focus when Form is loaded

Input

Load the Form

Expected Output

It Should be in the Username field.

Actual Output

Focus is on Username field.

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC002

NAME : Login

Purpose

Login into Engineering Module

Input

Valid Username,Password and have access permission of Engineering Module

Expected Output

Home Page for particular roles or error message

Actual Output

Correct Username and Password has entered by user

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC003

NAME : Database Operation Confirmation

Purpose

To ensure that operations are affecting database dynamically

Input

Insert data in Textbox, Select Dropdown

Expected Output

Data is Successfully inserted.

Actual Output

Invalid Column Name

Successful

No

Action Taken

In Insert query write correct column name.

TEST CASE ID : TC004

NAME : Check all Dropdown List

Purpose

Check all Dropdown List Values

Input

Select the Dropdown List.

Expected Output

Fetch the correct data from the existing database.

Actual Output

Invalid data in the Dropdown List

Successful

No

Action Taken

Check the property of Dropdown list and also check code.

TEST CASE ID : TC005

NAME : Numeric Validation

Purpose

Creating Project Details

Input

Enter numeric value in the Quantity Textbox

Expected Output

Numeric Value must be entered

Actual Output

Numeric Value is only entered in Quantity Textbox.

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC006

NAME : Auto Generation

Purpose

For auto generation is checked in all add entry forms.

Input

Click on New Button.

Expected Output

Generate the ID number by incrementing one to the last stored Id in the database.

Actual Output

Id is Auto Generated.

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC007

NAME : Menu Bar Validation

Purpose

Check the validation of menu bar.

Input

Click on the main name in the menu.

Expected Output

It opens with subtopics when it click.

Actual Output

Subtopics are opened on click.

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC008

NAME : Report Validation

Purpose

Generate report

Input

Select valid criteria for report generation

Expected Output

Display Crystal Report as per criteria from the database.

Actual Output

Crystal Report is generated.

Successful

Yes

Action Taken

Accepted

TEST CASE ID : TC009

NAME : Tab Validation

Purpose

Check Tab Indexes.

Input

Run the page

Expected Output

All tab focus has to be worked in correct sequence.

Actual Output

Tab focus is not working properly

Successful

No

Action Taken

Check the Tab index

TEST CASE ID : TC010

NAME : Database Validation

Purpose

Check field's name, type and size for each database table and against database design.

Input

Entering correct input fields as per requirement

Expected Output

Field's name, type and size should be consistent through out the database for a particular field.

Actual Output

Field's name, type and size is consistent.

Successful

Yes

Action Taken

Accepted

Writing Services

Essay Writing
Service

Find out how the very best essay writing service can help you accomplish more and achieve higher marks today.

Assignment Writing Service

From complicated assignments to tricky tasks, our experts can tackle virtually any question thrown at them.

Dissertation Writing Service

A dissertation (also known as a thesis or research project) is probably the most important piece of work for any student! From full dissertations to individual chapters, we’re on hand to support you.

Coursework Writing Service

Our expert qualified writers can help you get your coursework right first time, every time.

Dissertation Proposal Service

The first step to completing a dissertation is to create a proposal that talks about what you wish to do. Our experts can design suitable methodologies - perfect to help you get started with a dissertation.

Report Writing
Service

Reports for any audience. Perfectly structured, professionally written, and tailored to suit your exact requirements.

Essay Skeleton Answer Service

If you’re just looking for some help to get started on an essay, our outline service provides you with a perfect essay plan.

Marking & Proofreading Service

Not sure if your work is hitting the mark? Struggling to get feedback from your lecturer? Our premium marking service was created just for you - get the feedback you deserve now.

Exam Revision
Service

Exams can be one of the most stressful experiences you’ll ever have! Revision is key, and we’re here to help. With custom created revision notes and exam answers, you’ll never feel underprepared again.