






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
thesis system testing chapter is about how to testing theoretically system when u are creating actually system .
Typology: Thesis
1 / 10
This page cannot be seen from the preview
Don't miss anything!







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.
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.
It explains the process of giving the input to the system and checking the output, with
considering how the system generates the output.
The software is tested for functional requirement this check whether the application is behaving
according to the specification.
This testing check the system is performing properly according to user’s requirement.
This is also known as “testing for user Friendless”. It checks the case of use of an application.
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.
This type of software testing identifies the way in which installation procedure lead to incorrect
result.
This type of testing is performed to check how user friendly the application is the user should be
able to use the application.
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.
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.
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
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
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:
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: