Got a question on the topic? Please share it in the comment section below and our experts will answer it for you. For Edureka Test Automation Engineer Masters Curriculum, Visit our Website: bit.ly/2TZiTIk
thank you very much, very clear explanation. can you also explain and give examples of test case development and test environment setup in a real project. maybe the demo project.
Hey Andrew! QA/QC is the combination of quality assurance, the process or set of processes used to measure and assure the quality of a product, and quality control, the process of ensuring products and services meet consumer expectations. What is Smoke Testing? Smoke Testing is a kind of Software Testing performed after software build to ascertain that the critical functionalities of the program are working fine. It is executed ""before"" any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application so that the QA team does not waste time installing and testing the software application. In Smoke Testing, the test cases chose to cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionalities of the system are working fine. For Example, a typical smoke test would be - Verify that the application launches successfully, Check that the GUI is responsive ... etc.
What is Sanity Testing? Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing. The objective is ""not"" to verify thoroughly the new functionality but to determine that the developer has applied some rationality (sanity) while producing the software. For instance, if your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the advanced functionalities like sin 30 + cos 50. A Test Strategy document is a high level document and normally developed by project manager. This document defines “Software Testing Approach” to achieve testing objectives. ... Some companies include the “Test Approach” or “Strategy” inside the Test Plan, which is fine and it is usually the case for small projects."
Test case consist of test case name, Precondition, steps / input condition, expected result. Test scenario consists of a detailed test procedure. Test scenario is one liner statement which tell us about what to test. Test case means detailed documenting the cases which help executing while testing.
Got a question on the topic? Please share it in the comment section below and our experts will answer it for you. For Edureka Test Automation Engineer Masters Curriculum, Visit our Website: bit.ly/2TZiTIk
Thanks! This wonderful tutorial series saved me with clear explanation. I really struggle with my collegiate courses which I cannot understand at all.
You're welcome 🙂 Glad it was helpful. Keep learning with us!!
Shantani I like your videos.' You really explain very well. Each and every topic... Thanks
You're welcome 😊 Glad it was helpful!! Keep learning with us..
Pretty good detailing of STLC. Thank u so much for the tutorial.
thank you very much, very clear explanation.
can you also explain and give examples of test case development and test environment setup in a real project.
maybe the demo project.
Thanks for sharing this video about the software testing life cycle really helpful for students.
Nice Presentation.... Tq...Guys
Could you please tell me
How to write test cases for drop down box?
Thanks it was good information
Thank you, very good.
very informative video . Many thanks
Excellent
Thanks!
Welcome!
Difference between QA and QC?
Smoke and Sanity Testing?
Difference Between Test plan and Test stretgy?
Test case template
Hey Andrew!
QA/QC is the combination of quality assurance, the process or set of processes used to measure and assure the quality of a product, and quality control, the process of ensuring products and services meet consumer expectations.
What is Smoke Testing?
Smoke Testing is a kind of Software Testing performed after software build to ascertain that the critical functionalities of the program are working fine. It is executed ""before"" any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application so that the QA team does not waste time installing and testing the software application.
In Smoke Testing, the test cases chose to cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionalities of the system are working fine.
For Example, a typical smoke test would be - Verify that the application launches successfully, Check that the GUI is responsive ... etc.
What is Sanity Testing?
Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
The objective is ""not"" to verify thoroughly the new functionality but to determine that the developer has applied some rationality (sanity) while producing the software.
For instance, if your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the advanced functionalities like sin 30 + cos 50.
A Test Strategy document is a high level document and normally developed by project manager. This document defines “Software Testing Approach” to achieve testing objectives. ... Some companies include the “Test Approach” or “Strategy” inside the Test Plan, which is fine and it is usually the case for small projects."
Difference between test scenario and test case
Test case consist of test case name, Precondition, steps / input condition, expected result. Test scenario consists of a detailed test procedure. Test scenario is one liner statement which tell us about what to test. Test case means detailed documenting the cases which help executing while testing.