Scribd
Upload
114 views

Manual Testing Notes

The document describes daily activities in a software testing project, including understanding requirements, writing test cases, test execution, and defect reporting. It then provides an overview of the software development life cycle (SDLC) process, outlining the main stages from requirements analysis to delivery and maintenance. Finally, it details the software testing life cycle (STLC) process and key activities such as test planning, design, execution, defect reporting, and closure.

Uploaded by

victor othugadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
114 views

Manual Testing Notes

The document describes daily activities in a software testing project, including understanding requirements, writing test cases, test execution, and defect reporting. It then provides an overview of the software development life cycle (SDLC) process, outlining the main stages from requirements analysis to delivery and maintenance. Finally, it details the software testing life cycle (STLC) process and key activities such as test planning, design, execution, defect reporting, and closure.

Uploaded by

victor othugadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 3

What are daily activities in your project?

Understanding the testing requirements, identifying test scenarios, writing test cases and doing test
execution and defect reporting.

SDLC?

1. SDLC will explain all implementation activities of a project from day 1 to upto end of the project

2. As a S/w Engineer what are the activities that we have to perform everthing will be in SDLC process

3. SDLC Starts with

1.Requirements and understanding - S/w engineer should start nalysing the requirements and
understand the requirements what exactly client need

2.Planning - It is prepared by PM, After Analysing the requirements based on the requirements the PM
prepares the project Plan, duration,developers, Testers, designing team, Automation, os....

3.Designing - It is done by Technical team/Architect team

Based on requirements design team will design in 2 different WAYS

i) HLD: High level design: outlook of an application

ii) LLD: low level design: innerlook of an application

4.Coding - Based on requirments coding will be done by developers..

5.testing - once coding is done before giving to the testing team the developers will test the application
@there end

i) White box Testing: Testing done by developers

under white box Testing 2 levels

i) unit Testing: Testing each and every part of a code

ii) Integration Testing: Combining all parts of a code and conducting testing is called as
Integration/interconnected Testing

When 100% coding and white box Testing is done than the developers will give the application for
Testing---Entry Criteria

Black Box Testing:

-----------------------
Testing done by Testers

2 levels

i) System Testing: Compare the Expected to Actual value

expected: Client Requirement

Actual: Application developed

exp=Act--signoff

exp#Act--defect/Bug

ii) UAT(user acceptance Testing):After System Testing before submitting application to


client, Conducting testing along with Business Analyst

6.Delievery and maintenance

Delievery -Finally, Testing is completed we will release an application to client here

maintenance -

After release an application to the client, during utilisation if customer faces any problem we have to
support them

This is SDLC.

STLC: Process...

1.Test Planning - Test Strategy and Test Plan

2.Test Analysing - Analysing and understanding the requirements

3.Test design - Based on the reuqirements we have to prepare 2 types of documents:

1.Test Scenario - what to test

2. Test case - how to test

4.Test Environment - s/w and h/w configuration

5.Test Execution- Tc's should be ready as per the req.... build should release by the developer,
implementing all the tc's on the buld is called as test execution.

6.Defect Reporting - exp#actual result is called defect.

DEFECT is HIGH, MEDIUM AND LOW - DEVELOPERS


DEFECT IS VERY HIGH, SHOW SHOPPER - MANAGER

7.Test Closer?

when all the test cases are executed sucessfully and passed and when all the defects are succesfully
closed.

Defect report summary

BUG LIFE CYCLE -

You might also like