Software Testing Tutorial #2 - What is Manual Testing | With Examples

preview_player
Показать описание
In this Software Testing Tutorial we will learn what is manual testing and its process with examples. Software testing can be broadly categorized as Manual testing and Automation testing.

Manual testing is the testing which is done without involvement of any automation tools or scripts. The process of manual testing needs to be followed and manual test execution of scripts need to pass before you plan to automate those test cases.

Help me in spreading the knowledge, please hit LIKE, SHARE, and SUBSCRIBE for the latest tutorials. More tutorial playlists below:

🔶 ENROL IN MANY FREE TRAININGS ON RCV ACADEMY PORTAL 🔶

🔶 FOLLOW US ON TWITTER 🔶

🔶 LIKE US ON FACEBOOK 🔶

🔶 OUR TUTORIAL WEBSITES 🔶

🔶 GET MY TRAININGS ON UDEMY 🔶

#SoftwareTestingTraining #SoftwareTestingTutorial #SoftwareTestingBootcamp #SoftwareTesting #QA #QATraining #QATutorials #RcvAcademy #SoftwareTestingMentor
Рекомендации по теме
Комментарии
Автор

Notes:
- Manual testing is the process of testing software manually without the assistance of automation tools or scripts.
- It is the initial type of testing performed in a software testing team.
- Manual testing is followed by automation testing, where tools and scripts are used.
- Manual testing involves analyzing the requirements provided by the customer and identifying any gaps or discrepancies.
- Test planning is an essential phase where the overall testing approach is defined, including the methodology and test coverage.
- Test case creation is the process of designing and creating test cases for the identified requirements.
- Test execution is the phase where the actual testing takes place. Test cases are executed manually in the test environment.
- Defects or bugs are identified during the execution phase and logged for resolution by the developers.
- Defects are retested after being fixed by the developers, and if they pass, they are closed.
- Test reporting involves preparing reports to document the testing progress, results, and any open defects.
- In agile methodologies like Scrum, shorter iterations result in dynamic reports, while waterfall or V-model approaches require formal test exit reports.

manoj_mafiosi
Автор

Thanks so much for sharing your videos. I am in the process of switching from tech sales to becoming a QA Engineer. I will be starting a bootcamp next month (Feb 2024). Thanks for these free resources!

tyroncanady
Автор

Thank you sir for sharing these videos. Really very helpful for me. Detailed explanation

padmayadav
Автор

Just wanted to join in the chorus of appreciation for your work and contributions. I recently finished a bootcamp and am currently applying for work. These videos are really helping me do a full scale refresh of everything I've learned. Thank you!

Ketchupfakeblood
Автор

THANKS FOR EXPLAINING IN DETAILS YOU ARE ONE OF THE BEST THAT EXPLAINED WELL

anifaanifa
Автор

Great teaching. I love it. your explanation is so clear

emmanuelochuko
Автор

Thank you I really love your explanation well done

ollao
Автор

Thanks for your video and nice teaching, please write the words clearly, Thanks

bcfjemn
Автор

Hi im new subscriber here.. may i know where should i start in manual tester career?

jeffreytejada
Автор

Sir Doesn't this includes test environment setup?

hirukiruwanwellaa
Автор

what are the tools to be use again? it's my first time hearing their names sir

justathought
Автор

What are the requirements to completely understand testing? for example I don't know what is agile and scrum

riyadhanduke
Автор

Sir I have question that
Testing me jana galat hai kya as fresher

GautamKumar-qxrt
Автор

Wt is test case and test scenarios? Sir

gurukirannagaraj
Автор

Is it possible to learn and work in this area starting from scratch? I dont know much about software testing i currently work for apple at a call center im a mac advisor and i am really interested in being a software tester. The videos are very helpful thank you very much!!!

NightFireMix
Автор

In this video you are talking that if execution fails, we log jira & development team fix it. And tester have to retest it. Is this retest is the Sanity Test? Just wanted to check.
And your tutorials are great, helping me a lot for my upcoming interview. Thank you so much!

swarna
Автор

why we need manual testing when i can use automation ? why don't we choose easy option ?

PrettyThings
Автор

I know its not important but what is your name my teacher

munyahwacho
Автор

Summary
Manual testing involves testing software manually without the use of automation tools, with key phases including requirement analysis, test planning, test case creation, execution, defect logging, and reporting.

Highlights
🕹 Manual testing is done without automation tools.
📝 Phases include requirement analysis, test planning, test case creation, execution, defect logging, and reporting.
🔄 Collaboration is key in Agile methodologies like Scrum.
📊 Test reports can vary in length depending on the development approach.
🛠 Tools like Jira can streamline test case management.
🚀 Quality is everyone’s responsibility in Agile methodologies.
⏰ Waterfall approaches have longer testing cycles.

Key Insights
🧠 Manual testing is essential for ensuring software quality as it involves human intervention to detect defects that automated tools may miss. This hands-on approach allows testers to simulate real user interactions and uncover critical issues that could impact user experience.
📊 Collaboration in Agile methodologies like Scrum promotes transparency and communication among team members, leading to faster feedback loops and continuous improvement. By involving stakeholders early in the process, teams can align on requirements and deliver high-quality software incrementally.
📉 The shift towards Agile methodologies like Scrum emphasizes the importance of shared responsibility for quality among team members. This shift from a phased approach in Waterfall methodologies to a collaborative team effort in Agile frameworks highlights the evolution of software development practices towards more adaptive and customer-centric approaches.

Jester-qsll