Manual Testing

Lets first understand the manual testing terminologies..

SDLC (Software Development Life Cycle)

Requirement Analysis --> Planning --> Design --> Implementation --> Testing --> Maintainance

Basically there are two types in Testing

1) Static Testing (FRS,BRS)
2) Dynamic Testing (Unit Testing, Integration Testing, System Testing, UAT)

In Dynamic Testing , Unit and Integration Testing are done by mostly developers.
System Testing and User Acceptance testing are done by Testers.

also there is concept of Black Box, White Box and Grey Box Testing in testing terminologies.

Black Box (Coding Knowledge is not required)
White Box (Coding Knowledge is required)
Grey Box (Mix of both black and white box)

Lets Focus on a System Testing, where most of the Testers work.

• System Testing (Black Box Testing)

1) User Interface Testing (UI of application)
2) Functional Testing
3) Non-Functional Testing
4) Usability Testing

these are the types of system testing on which the testers have to do their best for the Quality of the Application.

1) GUI (Graphical User Interface) Testing

Element check, Error Messages, Screen Section , Readability check, Resolution test, alignment test, Font colour, Image Quality, Image Alignment, Spelling Check, User Friendly test, Attractiveness test, scrollbar test, disable fields, image size, Heading Alignment, UI element test , these all are comes under the User Interface Testing.

2) Functional Testing

Object Properties Testing, Database Testing, Error Handling , Calculations , Manipulations, Links Testing, cookies and session testing these are comes under the Functional testing.

3)Non Functional Testing

After functional testing the non functional testing is performed.

Performance Testing--> Load testing, stress testing, endurance testing ,spike testing, volume testing

security testing, recovery testing, compatibility testing, configuration testing, installation testing , sanity testing

4) Usability Testing

Easiness of Application, context sensitive help, How well the user is able to access Application

There are also other terminologies , we have to focus on..

Regression Testing, Smoke Testing(Initial build if the build is ready i.e. stability of the application), Sanity Testing (stable build, during the release phase to check the main functionality of the application)

Lets discuss on the each phase of the software testing life cycle and who is responsible for that phase and documentation of the phase.

1) Requirement Analysis--> Buissness Analyst , Test Manager, Test lead, Test Engineer, Stake Holders.(Project plan)
2) Test planning --> Test Manager, Test Lead, Test Engineer
(FRD - Functional Requirement Document)
3)Test case Development--> Test Lead, Test Engineer(FRD, Test Plan)
4)Environment Setup--> Test Lead, Test Engineer(FRD, Test Plan, Test Case)
5)Test Execution--> Bug Report, Test Lead ,Test Engineer(FRD,Test Plan, Test Case, Bug report)
6)Test Cycle Closure--> Test Manager ,Test Lead, Test Engineer(Test Report, Defect Report)

• Bug Tracking and Reporting in jira

Defects are classified on the basis of severity and priority.

Severity(seriousness and impact on application)
priority(Importance of defects)