Launching Of Software Without Testing 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.

Software testing is an important part of software engineering and it required significant amount of effort. Testing can best be defined as

A set of activities conducted with the intent of finding errors present in the software.

Why testing is required? (Justification):-

The developer has finished the implementation of EORMS (Enhance Online Retail Management System). In order to maintain high quality standards for the application, the developer is required to conduct various tests.

Software testing is an expensive activity and launching of software without testing may lead to cost potentially much higher than that of testing.

Therefore, the developer has conducted tests on each module for supporting system development. It is done to evaluate the implemented system works as it is expected to and whether the required results are achieved.

Who should do the testing?

Other then developer, certain other persons are also required to test the system. It is being done for the overall advantage of the system. Persons other than developer can easily able to find the errors because they are unknown to the system so they can enter large range of invalid inputs to the system.

Tester Type

Tester Name

Modules Tested

Administrator

Developer

Mr. Chandan Kumar

Ms. Sonia Arora

Login

Profile Management

Product Management

Norms Management

Report

Change Password

Password Recovery

Customer

Developer

Employee of Company

Employee of Showroom

Customer part of web application

Table 1: Showing the testing persons along with the modules they are testing.

Different Types of Testing Strategy Used:-

SL/No.

Method

Application

1

Unit Testing

During Unit Testing developer tests the functionality and non functionality for each module using both black box and white box testing. The problems which were finding during testing phase were successfully rectified, including significant errors such as error related to data input and validation.

2

Integration Testing

Once each module successfully passed through the unit testing, they are combining together to provide the functionality by intercommunication between those modules.

3

Usability testing

After each module of the system is passed through unit testing and integration Testing, the developer performs Usability Testing to check whether the system is able to follows the usability engineering principles or not.

4.

Compatibility testing

During Compatibility testing developer is run the application on different system and different browser to check whether the application is compatible for different browser or not.

Fig1: Different Levels of Testing

Functionality Testing (Black Box Testing) - It is not possible to all the test cases. So, there should be strategy to reduce this incompleteness as far as possible. One such approach is based on the functionality of the program and is known as functional testing. Here it mainly checks the output of the System on certain input. In Black Box Testing the user/tester does not concern about the source code.

Structural Testing (White Box Testing) - It is used to examine the internal structure of the program. The knowledge to the internal structure of the code can be used to find the number of test cases required to assurance a given level of test coverage.

Why White Box Testing is required? (Justification)

There might be parts of code, which are not fully exercised by the functional tests. There may be certain parts of the code, which are surplus to requirements. It may find those errors which may have missed by functional testing.

Types of Testing

Black Box Testing

White Box Testing

Unit Testing

Applicable

Applicable

Integration Testing

Applicable

Not Applicable

Usability Testing

Applicable

Not Applicable

Compatibility Testing

Applicable

Not Applicable

Table summarizing different types of testing to be used: - (Glenford, J, 2004)

Table 2: Showing the testing persons along with the modules they are testing.

As mention in the above table the developer use Black Box testing in broad category. For example, though integration testing use both Black Box & White Box testing but the developer is only use black box testing for integration testing. It is as per the necessity of the given project. Justification and definition of different types of testing are given in the following sections.

Why Test Cases are required for testing? (Justification)

Test case illustrates an expected output description for a given input description. Test case is relevant for all type of testing. A good quality test case has high possibility of finding an error.

Unit Testing/Module Testing -

Justification for Using Unit Testing in the given project: -

Unit testing is used at the module level. It is easy to locate an error fairly easily as the size of a single module is small enough. Moreover, while applying unit testing, confusing interactions of multiple errors and widely different parts of the software are eliminated.

Functionality Unit Testing

Module Name : Login

Test Case ID

TC-01

Test Date

2nd march to 3rd march

Duration

6 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To validate the proper working and validation of Login module.

1st Testing (Test Data)

In login module, the user has to enter username and password details. After entering login details, the user should click login button to enter into the system.

Input Field Obligations Only Username or Password is entered

Expected Result

User can Login into the system

Length of password should not less than 6 and both username and password is mandatory.

Actual Result

User can not able to Login into the system

Server is not able start at the time of run the application

Remark

Due to the problem encountered in starting in the Server the application is not able to connect to the database EORMS

Port number is not valid in the Database manager connection String source code of the program.

2nd Testing (Test Data)

In login module, the user has to enter username and password details. After entering login details, the user should click login button to enter into the system.

Input Field Obligations

Expected Result

User can Login into the system

Actual Result

Identical to the expected result.

Remark

…………….NIL……………

………NIL……….

Functionality Unit Testing Module: Profile Management

Test Case ID

TC-02

Test Date

2nd march to 3rd march

Duration

6 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To validate the proper working and validation of sub modules of Profile management like Company Showroom Registration, View Showroom Profile, and Update existing Company Showroom Profile.

1st Testing (Test Data)

Valid email id should be entered in the email id field. Password should not less the size length of 6. Username, Password and status should not be null.

Input Field Obligations

Expected Result

Validate the test input data, trying to open the port connectivity for the data server and prompt the message showroom has successfully registered to the system

Invalid email id and other invalid input obligations are not allowed.

Actual Result

Add User test Failed.

Server is not able start at the time of run the application

Remark

Due to the problem encountered in starting in the Server the application is not able to connect to the database EORMS

Port number is not valid in the Database manager connection string source code of the program.

2nd Testing (Test Data)

Valid email id should be entered in the email id field. Password should not less the size length of 6. Username, Password should not be null.

Input Field Obligations

Expected Result

Successfully registration of the showroom to the system

Invalid email id and other invalid input obligations are not allowed.

Actual Result

Identical to the expected result.

Administrator/Company Employee was able to add a new user to the application successfully.

Remark

Due to the problem in connection string it didn't allow to adding the input test data to the showroomregistration table.

………NIL……….

Functionality Unit Testing

Module: View Showroom Information

Test Case ID

TC-03

Test Date

2nd march to 3rd march

Duration

6 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To validate the proper working and validation of View Showroom Profile Information feature.

1st Testing (Test Data)

Administrator can be able to view the showroom profile by clicking in view showroom profile it show all showroom profile details.

Input Field Obligations

Expected Result

Validate the test input data, trying to connect with the data server and then search for specific data request and finally serve the request with proper response in a tabular format.

No input is required from User

Actual Result

Identical to the expected result.

Administrator/Company Employee was able to view all it respective showrooms information.

Remark

The process of successful complications depends upon the successful query invocation through company registration DAO (Data Access Objects).

………NIL……….

Functionality Unit Testing

Module: Product Management

Test Case ID

TC-04

Test Date

4th march to 6th march

Duration

6 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To validate the proper working and validation of all sub modules of product management such as Add Product, View Product Info, and Update Product Info.

1st Testing (Test Data)

Valid test input data should be entered. Administrator/Company Employees are required to manually feed product details such as product name, product max retail price; user can select product categories and sub category suitable for product from respective drop down menus.

Input Field Obligations

Expected Result

Validate the input data, trying to open the port connectivity with the database EORMS and prompt the message Product has successfully registered to the products table.

Product name and product maximum retail price are mandatory for registration of new product.

Actual Result

Add product test Failed.

Product category and sub category fields cannot be left null.

Remark

In the JSP view if product category and sub category will be null can't be added to the products table.

2nd Testing (Test Data)

Valid test input data should be entered. Administrator/Company Employee required to manually feed product details such as product name, product max retail price and admin/company Employee can select product categories and product sub category suitable for product from respective drop down menus.

Input Field Obligations

Expected Result

Validate the test input data, trying to open the port connectivity to data server and prompt the message Product successfully added to the system

Product name and product maximum retail price are mandatory input fields to add the product to database.

Actual Result

Identical to the expected result.

Administrator was able to add a new product to the application successfully.

Remark

The product category and product sub category required to be selected in order to differentiate the product.

………NIL……….

Functionality Unit Testing

Module: Norms Management

Test Case ID

TC-05

Test Date

4th march to 6th march

Duration

2 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To verify the proper working and validation of Norms Assortment.

1st Testing (Test Data)

For Assigning norms of product to particular showroom. Showroom field is required to be selected from drop down menu. Administrator/ Company Employee can search the products based upon product categories or admin can directly click on search button to view all assigned products to the respective showroom from database. For assigning norms of product to showroom administrator/ Company Employee manually required entering the norms value for each product. By default norms of each product to the showroom is Zero. If without editing norms value administrator/ Company Employee click on update norms then there will be no change in the value stored in the norms table of EORMS database.

Input Field Obligations

Expected Result

Verifying the test input data, trying to open the port connectivity to data server and then invoking queries to update the level of norms from zero to the defined value determined by the administrator.

Showroom name should not be left blank in order to proceed with Norms Assortment.

Actual Result

Identical to the expected result.

Administrator/ Company Employee were able to assign the norms of product to particular showroom successfully.

Remark

The product Assignment process completely depends upon successful invocation of update query which will update default value of norms from zero to the given value by administrator.

Functionality Unit Testing

Module: Sale Report

Test Case ID

TC-06

Test Date

8th march to 10th march

Duration

2 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To verify the proper working and validation of Daily Sale Report. Whether it is able to retrieve the sales data of various showrooms registered to the application.

1st Testing (Test Data)

Sale Report requires proper working of sale management module because it retrieves data from their only

Input Field Obligations

Expected Result

Verifying the test input data, trying to open the port connectivity to data server and then invoking queries to retrieve the sale of products from particular showroom.

Showroom name should not be left blank in order to proceed with Sale Report.

Actual Result

Identical to the expected result.

Administrator/Company Employee was able to view the sale register of particular showroom successfully.

Remark

The sale register process depends upon sale management module which is visible in the profile of showroom. When sale of products is being completed from a showroom profile it is visible in the profile of sale report of administrator/Company Employee account. To view the sale report of showroom first it is required to select the showroom and based upon the showroom name sale table is invoked to retrieve the data from it.

Functionality Unit Testing

Module: Sale Management

Test Case ID

TC-07

Test Date

15th march to 20th march

Duration

10 Hours

Testers

Developer(Bhaskar Jyoti Gayan)

Test Objective

To verify the appropriate working and validation of Sale Management. Sale Management module helps all respective Company showrooms to sale their products successfully and based upon the sale of their product showroom current stock is changed, which further determines Sale Report of that showroom.

1st Testing (Test Data)

Valid test input data should be entered. Company Showroom is required

Input Field Obligations

Expected Result

Verifying the test input data, trying to open the port connectivity to data server and invoke the queries to retrieve assigned product by administrator for the particular showroom and then again invoking the query to successfully add the product to sales table.

The invoice number should not be more than data size of ten and it should be integer. Invoice date should be in the form of date.

Actual Result

Sale Management of showroom failed.

Sale management was not successfully implemented due to invalid data size error. There was mismatch of type defined in physical database and code invoked.

Remark

In the context Model (Data Access Object, Bean) it is mandatory for the match of physical database data type and the code where developer is storing the variables. There should be match between data type.

2nd Testing (Test Data)

Valid test input data should be entered. Showroom is required to enter the invoice number and invoice date and showroom can go for advance search of products from drop down menu list. Showroom can also select the option of search directly and view their assigned products from administrator. Showroom manually requires feed the numbers of products inside the field and after selecting add the product will successfully be added to sale account of that showroom id.

Input Field Obligations

Expected Result

Verifying the test input data, trying to open the port connectivity to data server and invoke the queries to retrieve assigned product by administrator for the particular showroom and then again invoking the query to successfully add the product to sales table.

The invoice number should not be more than data size of ten and it should be integer. Invoice date should be in the form of date.

Actual Result

Identical to the expected result.

Manager was able to add the product to their sale account information respectively and simultaneously showroom current stock has also been updated.

Remark

Sale management module successfully tested there were no data type mismatch and queries to update showroom's account was successfully updated.

Integration Test:

Functional Integration Testing

Module: Administrator/Company Employee

Test Case ID

IT-01

Test Date

15th to 30th march

Test Duration

5 hours

Testers

Developer, Mr. Chandan Kumar, Bhaljeet Singh

Test Data

Expected Result

Actual Result

Registered Company's Employee can login into the Enhance Online Retail Management System with valid username and password.

When the valid username and password are provided to the system, the application should allow the Administrator/ Company Employee to perform Administrative tasks.

The output is same as expected result

Administrator/Company Employee Can able to perform registration of new showroom to the EORMS.

After providing valid login credential to the system; Employee of Company can able to registration of new showroom to the system.

The output is same as expected result

Administrator/Company Employee is able set the norms of its respective showroom.

After providing valid login credential to the system; Employee of Company can able to set the norm of products for their respective showroom the system.

The output is same as expected result

Usability Testing

Usability Testing was conducted to evaluate and ensure that system users are able to use the system without any confusion and find it useful. Testers, which were involved in Functional and Integration testing, were also the part of usability testing in order to determine the usability strengths and weaknesses of the system.

Feature Applied

Questions

Answers

Menu Bars

Are menu labels meaningful?

Yes

No

N/A

Are they describing association?

Yes

No

N/A

Link

Are Links meaningful?

Yes

No

N/A

Do they result correct action?

Yes

No

N/A

Are Links following the visibility feature of Human Computer Interaction & usability?

Yes

No

N/A

Are Links arranged properly?

Yes

No

N/A

Text Boxes

Do the maximum length of the text box matches their corresponding data storage sizes?

Yes

No

N/A

Do the check constraints available

Yes

No

N/A

Combo Boxes

Are they placed in a meaningful way?

Yes

No

N/A

Do combo box have appropriate values?

Yes

No

N/A

Does the selection change the result?

Yes

No

N/A

Screen Design

Is the Layout of web application is appropriate for user to perform task?

Yes

No

N/A

Do graphics and text are arranged on HCIU pattern?

Yes

No

N/A

Color

Do colors applied in menu and submenu is appropriate?

Yes

No

N/A

Do colors applied in table's row and columns are appropriate?

Yes

No

N/A

Do color labeling is matching industry pattern?

Yes

No

N/A

Messages

Are error message consequential and expressive?

Yes

No

N/A

Are error message misleading the user?

Yes

No

N/A

Fonts

Is there consistency of fonts used?

Yes

No

N/A

Are the fonts impressive?

Yes

No

N/A

Check Boxes

Do check boxes showing their status (checked/unchecked) and working as per that?

Yes

No

N/A

Do they result in proper action?

Yes

No

N/A

Conclusion: Above result shows that the graphical user interface of the proposed system (Synchronized Replenishment System) is user friendly. Therefore developer found that the end users definitely not feel any difficulty in accessing Synchronized Replenishment System.

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.