Manual Testing

Vaibhav Darandale — Sun, 30 Aug 2026 14:21:22 +0000

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)

Roadmap to Playwright Automation Engineer in 2026 :)

Vaibhav Darandale — Wed, 26 Aug 2026 13:23:46 +0000

"Quality is not an act,it is a habit !"

Hello guyz, if you are looking for a blog ,article that helps you to become an Automation Engineer in 2026 , here it is!!!

lets talk about technical background require for an Automation Engineer,
there is not much technical stuff, just your Dedication for around 3-4 months and consistency.

Actually you are 4-5 steps away from it. lets discuss about it.

*1. Manual Testing.
*
it is mandatory process to become an Automation Engineer.there are 5 modules you have to understand from basics.

Software Testing Concepts(What)
Software Testing Life Cycle
Software Testing Projects and Templates
Agile Testing and Jira tool
Usage of AI in Manual Testing

*2. Programming Core Java/Javascript/Typescript/Python
*
You have to learn any one programming language from above list.
choose any one and practice daily till you have command on that language, i suggest Typescript or Python based on current situation and demand in job market 2026.
I prefer these because in job market , playwright tool is most demanding these days.

*3. Web Automation(Playwright)
*
To master Playwright web automation, you should approach learning through a structured, modular roadmap. Since Playwright is an ecosystem rather than a monolithic tool, breaking it down into specific core concepts, tool modules, and advanced framework modules will help you build highly stable, professional-grade test suits.

Core Automation Foundation(Targeted Locators,Auto waiting and Actionability,Basic UI interaction, Web first assertions)
The Playwright Tooling Suite(Code Generator,UI Mode and Playwright Inspector,Trace Viewer)
Advanced Browser and Page Management(Browser Contexts,Stage Storage Authenticating Sharing,Frames and Windows,Emulation and Geolocation)
Network and API Automation(API Testing via UI Contexts,Network Interception and Mocking)
Architecture and Framework Engineering(Page Object Model,Custom Fixtures,Data Driven Testing,Configuration and Reporters)
DevOps, Cloud and AI Integration(CI-CD Integration ,GitHub Actions,Docker Containerization, Visual Regression Testing,AI Assistance MCP nad CoPilot)

*4. API Testing (Postman)
*
To master API testing with Postman, you should structure your learning into four core phases: Fundamentals, Automation & Scripting, Advanced Testing, and CI/CD Integration

Core Fundamentals(HTTP Methods and Endpoints, Request Anatomy, Inspecting Responses, Collections, Variables and Environments)
Automation and Scripting(Pre Request Scripts,Post response Scripts Tests, JSON Response Parsing, API Chaining, Collection Runner)
Advanced Testing Scenarios(API Authentication, Data Driven Testing ,Mock Servers, Postman Console and Debugging)
CI CD and Team Collaboration (Newman CLI, CI CD Pipeline Integration, Reporting, Workspaces and Collaboration)

*5. CI CD For Quality Assurance
*
To learn CI/CD (Continuous Integration and Continuous Delivery) for Quality Assurance (QA), you should break your learning path into core concepts, key tools, and hands-on pipeline integration.

CI CD Fundamentals for Testers.
Version control and Git Basics
Essential CI CD Tools(Jenkins, GitHub Actions, GitLab CI/CD,)
Containerization With Docker
Integrating Tests into Pipelines.

At the end, practice all these 5 modules and you will be Automation Engineer :)

DEV Community: Vaibhav Darandale

Manual Testing

Roadmap to Playwright Automation Engineer in 2026 :)

"Quality is not an act,it is a habit !"