One of the biggest advantages of manual testing is the human touch. Testers think like real users and evaluate how the application feels in real-world scenarios. They can detect issues related to usability, design, and user experience that automated tools cannot easily identify.
For example, a button might be technically working fine, but its placement or color may confuse users. A manual tester can quickly notice such issues.
In today’s fast-evolving digital world, software applications have become an essential part of our daily lives. From mobile apps to banking systems and e-commerce platforms, users expect applications to be reliable, user-friendly, and error-free.
Here what exactly manual testing is-
Manual Testing - Testing the software or application repeatedly or again and again manually in order to find the defects in the software according to the customer.
Real time example for manual testing-
[Customer] ---->Google
[Requirements]----->[1000 page document] ---[MS -excel/Ms word]
software Company
1.BA (Business Analyst)
(Requirement Collection)
2.Developers
Developer will look into requirement and - 50 lakh line codes
write a code and develop the software or Application
Developer will compress code into exe-files /set-up files
“gmail.exe” gmail.exe
Install the gmail software
*Developer will give url, username, password
*Test Engineer will get url, username, password
Test Engineers
1.Test Engineer will manually switch on the computer.
2.Test Engineer will manually check for internet.
- Test engineer manually open the browser. 4.Test Engineer will manually enter the url- www.gmail.com 5.Welcome login page is displayed. 6.Test Engineer will manually enter the username and password and click on login button 7.Home page is displayed. 8.Test Engineer will manually click on compose and enter values for all the fields and click on send button 9.Test Engineer manually click on ‘sent items’ | \ | \ | \ [Mail is not displayed] [Mail is displayed] If it shows blank-defect in it shows pass in manualtest manual testing
Note:-While Testing software if test engineer finds any defect then TE communicate defect to the developers.
Developer will fix the defect and give new software.
Test Engineer or developer will uninstall the old software and install the new software.
And test engineer manually test defect is fixed or not.
Difference between Developer and Test Engineers
Developer
1.Developer will look into requirement
Write the code and develop the software.
2.Developer will be fixing the defect.
Test
-
Test Engineer look into the requirement
And test the software.
2.Test Engineer will be finding the defect.In the software development life cycle Waterfall model 2. Derived model
Spiral model 4. Hybride model
Verification and validation model 5. Agile model
Prototype Model
*SDLC is a step by step procedure or standard procedure to develop a new software.
*When a person or a company wants to start with new project they should follow sdlc model.
In the condition if we don’t follow the sdlc model
- We will no get to know how many engineers are required to work on the project.
- We will not get to know how much cost should be invested to work on the project.
- There might not be proper supporting requirement document.
Stages of SDLC models BA (Business Analyst)
[Requirement Collection]
PA (Product Analyst)
[Feasibility Study] BA
Architech
HR Team
HLD
[Design] Archietect/Technical Architect
LLD
[Coding] Sr developer/Jr developer
[Testing] Sr Test engineer
[Installation/Implementation] IT engineer
developer
[Manitainanace]
Test engineer
Water fall model
Water fall model is a step by step procedure or standard procedure to develop a new software.
[Requirement Collection]
[Feasibility study]
[Design]
[coding]
[Testing]
[Installation]
[Maintainence]
Requirement Collection- It is nothing but collection of requirement from the customer place it is done by BA or PA.
Ba from the company will go to customer place and collect the requirement in business language come back to company convert BL into software language and explain to developer, TE, Architect. This process is called Requirement Collection.
Feasibility Study -Once after requirement collection is done then we go for feasibility study.
*It is a team which consists of project manager, BA, Architect, finance team, HR team
*This is the stage where company decides to take up the project or not.
*This is the stage where company get to know if we take
Roles of project Manger
Project manage will interact with the finance manager, HR team, Architect, BA and decide to take up the project or not.
*He will gather all the information regarding the project.
*HR Team and Finance team is optional.
Role of Architect
Architech will think from technical point of view and he will also think technically is it possible to implement the project or not.
----If we are able to implement which technology to be used such as java,c,python etc.
Role of BA
He will be involved in requirement collection.
Role of Finanace Team
Finance team will think from money point of view They will also think what is the operational cost required to work for the project
And If they invest money do they get profit or not.
Role of HR Team
Hr team will think from hiring point of view.
They will check how many experience resource and how many fresher resource are requires for the project.
Design
once after the feasibility study is completed company decided to take up the project then we go for design stage which is done by architech.
High level Design – Designing the architecture of the software is called as high level design
Low Level design – if you take any application then designing each and every indivual module in detail is called low level design.
Coding
Once after design is completed then we go for coding stage. It is done by the sr developer and junior developer by looking into the requirement
Testing
Once after coding completed developers will give software to test engineer all the test engineer will start to test the software by entering all possible inputs into the software to find the defect in the software.
Installation
Once after testing is completed software quality is good then we go for installation phase or stage it is done by IT
Maintainance-
Once after installation is completed then we go for maintainance stages.
Software Testing
White box testing grey box testing Black box testing
White box testing
Testing each and every line of the code is called white box testing.
Grey box Testing
Top comments (0)