system testing chapter, Thesis of Computer Science

thesis system testing chapter is about how to testing theoretically system when u are creating actually system .

Typology: Thesis

2018/2019

Uploaded on 09/02/2019

zain-ullah-1
zain-ullah-1 🇵🇰

1 document

1 / 10

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
ONLINE MARKET
61
Chapter 8 System Testing
Chapter 8
System Testing
8.1 Introduction
Testing software is operating the software under controlled condition to verify that it behaves “as
specified” to detect errors and to validate what has been specified and what the user actually
wanted. Most of the time software project are not estimated properly and tend to run behind
schedule when it come meeting the deadline, people seem to ignore a very important phase in the
whole processing. Testing System testing is an essential step for the development of a reliable
and error free system.
Good testing involves much more then just running the system processes as normal input. Good
testing involves much more than just running the program a few time to see whether it works.
A successful test is the one that find errors.
Our project “ONLINE MARKET” has been thoroughly tested by us/clients.
8.2 Software Testing Types
Software testing life cycles is process that explain the flow of the test that are to be carried on
each product .Some major types of software testing are.
8.2.1 Black Box Testing
It explains the process of giving the input to the system and checking the output, with
considering how the system generates the output.
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download system testing chapter and more Thesis Computer Science in PDF only on Docsity!

Chapter 8

System Testing

8.1 Introduction

Testing software is operating the software under controlled condition to verify that it behaves “as

specified” to detect errors and to validate what has been specified and what the user actually

wanted. Most of the time software project are not estimated properly and tend to run behind

schedule when it come meeting the deadline, people seem to ignore a very important phase in the

whole processing. Testing System testing is an essential step for the development of a reliable

and error free system.

Good testing involves much more then just running the system processes as normal input. Good

testing involves much more than just running the program a few time to see whether it works.

A successful test is the one that find errors.

Our project “ONLINE MARKET” has been thoroughly tested by us/clients.

8.2 Software Testing Types

Software testing life cycles is process that explain the flow of the test that are to be carried on

each product .Some major types of software testing are.

8.2.1 Black Box Testing

It explains the process of giving the input to the system and checking the output, with

considering how the system generates the output.

8.2.2 Functional Testing

The software is tested for functional requirement this check whether the application is behaving

according to the specification.

8.2.3 Performance Testing

This testing check the system is performing properly according to user’s requirement.

8.2.4 Usability Testing

This is also known as “testing for user Friendless”. It checks the case of use of an application.

8.2.5 Recovery Testing

Recovery testing is very necessary to check how fast the system is able to recover against any

hardware failure catastrophic problem or any type of system crash.

8.2.6 Installing Testing

This type of software testing identifies the way in which installation procedure lead to incorrect

result.

8.2.7 User interface testing

This type of testing is performed to check how user friendly the application is the user should be

able to use the application.

  1. While the developers are ready with the code, the SQA team will be ready for testing. The testing phase is no longer a bottleneck for product delivery because the SQA team has been involved since the start of the project.

8.4 System testing plan

A test plan is a document detailing a systematic approach to testing software.

A test plan document strategy that will be used to verify and ensure that product or system meet

is design specification and other requirements, the major phases of software need test plans

because the focus and emphases of testing will change over the time. Testing new software in

developments is very different from testing software that has been running for some time while

testing a software we need to decide that what will be test, understand the software. The software

should have a concerned explanation of the “vision” behind its creation and the hoped for “path

“for its success. If the software has no such explicit statement should be the first goal.

8.5 Testing Metrics

In software development process most bugs are result of poor design. It is important to realize

that when you develop software bug will appear. Instead of trying to create a bug free product

your goal should be to achieve software of good quality.

It is important to track the number of bugs found over the time. Another metric to

determine your software quality is the bug discovery trend. This technique is commonly used at

sum it involves determining the ratio of number of hours it takes to find the next bug.

8.6 Software Bug

A software bug is an error, flow, mistake, failure or fault in a computer or a computer or system

that produced an incorrect or unexpected result

8.7 Testing of Project

The testing of our proposed system is under gone through all stages of black box testing and

white box testing. In evaluation phase, the system is reviewed to see whether the objective of the

system are accomplished or not. The testing of ONLINE MARKET is as follow.

 Trace _ability test matrix  Test case description

Trace-ability Matrix

Test Case ID Test Result

Test1 Verify that user get error messages on wrong user name and password.

Test has Passed Successfully. Test2 Verify that user get message on registration of two same email address

Test has Passed Successfully. Test3 Verify^ that^ user^ can’t^ access^ administrator account.

Test has Passed Successfully. Test4 Verify that products have been displayed.^ Test has Passed Successfully. Test5 Verify that no of items and total price are displayed in minicart when items are added in

Test has Passed Successfully.

Objective: Verify that user get error messages on wrong user name or password. Product/Version/Module: ONLINE MARKET. Environment: Windows 7 Pre-Requisite: User must enter user name or password.

Method: 1 Open Admin form 2 Enter username and password. 3 Then press the sign in button. 4 You will get the error message on incorrect username or password.

Test Case ID: Test 2 Test Engineer: Mr. Nasir Rashid Test Date: 15-011-2017 Test Case Version: Vr: 1.

Objective: Verify that user can’t access administrator account. Product/Version/Module: ONLINE MARKET. Environment: Windows 7 Pre-Requisite: User must enter user name and Email Address.

Method: Open login and enter user name and password. 1 Enter user name. 2 Enter password. 3 You will get the error message.

Test Case ID: Test 3 Test Engineer: Mr. Nasir Rahid Test Date: 15-011-2017 Test Case Version: Vr: 1.

Objective: Verify that products have been viewed. Product/Version/Module: ONLINE MARKET. Environment: Windows 7 Pre-Requisite: User has to visit the Home, Products and Category pages etc.

Method:

  1. Just open Home, Product and Category pages on our website.
  2. You will see all the products are displayed successfully.

Test Case ID: Test 4 Test Engineer: Mr. Nasir Rashid Test Date: 15-11-2017 Test Case Version: Vr: 1.

Objective: Verify that items and weekly price have been viewed when user clicks on weekly prices link. Product/Version/Module: ONLINE MARKET. Environment: Windows 7

Method:

  1. Visit Admin section, Enter authorize person name and password.
  2. Try to update, Add and delete Admin.
  3. Admin will be updated, Add and deleted successfully.