




Manual testing is the process of manually testing software
for defects.
It requires a tester to play the role of a...
Acceptance
Testing

Client Needs

System Testing

SRS

Integration
Testing

Design

Unit Testing

Code

Levels of testing
...
DEV1-login

DEV SERVER

CIT

DEV2Registration
SIT
DevN

Alpha

PRODUCTION

PRE-PROD

UAT

TutorialsBook www.tutorialsbook....








Unit Testing: This initial stage in testing normally
carried out by the developer who wrote the code and
somet...
Module
Test Plan

Test Unit

Combine unit
into modules

Module test

System test

Acceptance
test

System Test
Plan

SRS

...










It is used in both big and small projects.
The test cases can be added or removed
according to the movement...






By using manual testing, you cannot find the size
difference of the GUI object and color combination
easily.
In t...
Planning is most appropriate step when you have
to start the testing. You need to carry on with
manual testing or automate...










The test plan describes the testing objectives, the testing
scope, the testing approach, and the methodolog...






A test case is usually a single step, or
occasionally a sequence of steps, to test the
correct behavior/functiona...
 Analyzing requirements: To write a good test case,

a tester needs to understand the requirement. In
what context the re...
 Executing test cases (test execution): Once all the

test cases are written, they need to be executed.
Execution starts ...











Steps - A logical sequence of steps the tester must
follow to execute the test case
Expected Results - Th...





Blocked - Tester could not execute the test case
because of bug
Skipped - Test case was not executed this round
Bu...
Test Case:
File Open#

Test Description

N/A

Set up for [Product
Name]

Test cases/ Pass
Samples
/
Fail

No.
of
Bugs

Bug...
Upcoming SlideShare
Loading in …5
×

www.tutorialsbook.com presents Manual testing

677 views

Published on

This is free online software manual testing powerpoint.for more tutorials please visit www.tutorialsbook.com

Published in: Education, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
677
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
45
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

www.tutorialsbook.com presents Manual testing

  1. 1.    Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases. TutorialsBook www.tutorialsbook.com
  2. 2. Acceptance Testing Client Needs System Testing SRS Integration Testing Design Unit Testing Code Levels of testing TutorialsBook www.tutorialsbook.com
  3. 3. DEV1-login DEV SERVER CIT DEV2Registration SIT DevN Alpha PRODUCTION PRE-PROD UAT TutorialsBook www.tutorialsbook.com
  4. 4.     Unit Testing: This initial stage in testing normally carried out by the developer who wrote the code and sometimes by a peer using the white box testing technique. Integration Testing: This stage is carried out in two modes, as a complete package or as an increment to the earlier package. Most of the time black box testing technique is used. However, sometimes a combination of Black and White box testing is also used in this stage. System Testing: In this stage the software is tested from all possible dimensions for all intended purposes and platforms. In this stage Black box testing technique is normally used. User Acceptance Testing : This testing stage carried out in order to get customer sign-off of finished product. A 'pass' in this stage also ensures that the customer has accepted the software and is ready for their use. TutorialsBook www.tutorialsbook.com
  5. 5. Module Test Plan Test Unit Combine unit into modules Module test System test Acceptance test System Test Plan SRS Acceptance Test Plan Client Requirement Testing Process TutorialsBook www.tutorialsbook.com Interconnect Modules
  6. 6.      It is used in both big and small projects. The test cases can be added or removed according to the movement of the project. Within a limited cost budget you can finish this testing. Manual testing is better than automated testing in terms of reliability. Tester can execute additional ad-hoc. You will find that more bugs and errors are found with adhoc than the automation. TutorialsBook www.tutorialsbook.com
  7. 7.    By using manual testing, you cannot find the size difference of the GUI object and color combination easily. In this type of testing, the real performance and load cannot be determined for a huge number of clients. Manual testing is time consuming. TutorialsBook www.tutorialsbook.com
  8. 8. Planning is most appropriate step when you have to start the testing. You need to carry on with manual testing or automated testing easily. Whether you go for any one of the types of testing, you need to follow the following things:  Test planning  Writing test cases  Executing test cases  Reporting results of test cases TutorialsBook www.tutorialsbook.com
  9. 9.      The test plan describes the testing objectives, the testing scope, the testing approach, and the methodology used to conduct testing. Any hardware, software, and other tools required for testing should be included in the document. Test coverage in the test plan states what requirements will be verified during what stages of the product life. Test methods simply states how the test coverage will be implemented. Test plans also indicate which group or groups within the organization will be responsible for performing the test. TutorialsBook www.tutorialsbook.com
  10. 10.    A test case is usually a single step, or occasionally a sequence of steps, to test the correct behavior/functionalities, features of an application. An expected result or expected outcome is usually given. Test cases are often referred to as test scripts, particularly when written. Written test cases are usually collected into test suites. TutorialsBook www.tutorialsbook.com
  11. 11.  Analyzing requirements: To write a good test case, a tester needs to understand the requirement. In what context the requirement is described and what needs to be tested and how. What must be the expected result etc?  Writing test cases (test designing): A test case is developed based on the high level scenarios, which are in turn developed from the requirement. So, every requirement must have at least one test case. This test case needs to be wholly concentrated on the requirement. TutorialsBook www.tutorialsbook.com
  12. 12.  Executing test cases (test execution): Once all the test cases are written, they need to be executed. Execution starts only after the testing team receives the build from the development. Development and testing has to go parallel. While executing test cases, there will always a possibility that the expected result can vary from the actual result while testing. In this case, it is a defect/bug. A defect needs to be raised against the development team, and this defect needs to be resolved as soon as possible based on the schedule of the project. A test case is identified by ID number and prioritized. Each test case has the following criteria:  Purpose - Reason for the test case TutorialsBook www.tutorialsbook.com
  13. 13.       Steps - A logical sequence of steps the tester must follow to execute the test case Expected Results - The expected result of the test case Actual Result - What actually happened when the test case was executed Status - Identifies whether the test case was passed, failed, blocked or skipped. Pass - Actual result matched expected result Failed - Bug discovered that represents a failure of the feature TutorialsBook www.tutorialsbook.com
  14. 14.    Blocked - Tester could not execute the test case because of bug Skipped - Test case was not executed this round Bug ID - If the test case was failed, identify the bug number of the resulting bug. Attaching requirements (QA Matrix): QA matrix is used to assess how many requirements have been tested and have test cases written for them. It is in the form of a excel sheet, which shows whether a requirement is covered or not. TutorialsBook www.tutorialsbook.com
  15. 15. Test Case: File Open# Test Description N/A Set up for [Product Name] Test cases/ Pass Samples / Fail No. of Bugs Bug# Setup ____ ____ ____ 1.1 Test that file types supported by the program can be opened 1.1 P/F # # 1.2 Verify all the different ways to open file (mouse, keyboard and accelerated keys) 1.2 P/F # # 1.3 Verify files can be open from the local drives as well as network 1.3 P/F # # TutorialsBook www.tutorialsbook.com Comments

×