What is Scenario Testing?

Scenario testing is a software testing technique that makes best use of scenarios. Scenarios help a complex system to test better where in the scenarios are to be credible which are easy to evaluate.
As tester you should put yourself in end user’s place and figure out the real worlds scenario and use cases of the application under test 
Method in Scenario Testing

  • System scenarios
  • Use-case and role-based scenarios
Business Scenario
Business scenario is a hypothetical story that helps us to think the system behavior for a given condition or set of conditions the following example shows different ways of looking business scenario
  • A scenario can be considered as a process from point A to point B
  • Every alternative path can be consider as another scenario
  • Variables that can be consider as another scenario
  • Variable that can produce different results can be considered as different results can be considered as different scenarios
  • Negative test on how the system responds when invalid or sequence is applied
What is Test Coverage?
Test coverage is defined as a metric in Software Testing that measures the amount of testing performed by a set of test. 
It will include gathering information about which parts of a program are executed when running the test suite to determine which branches of conditional statements have been taken.
In simple terms, it is a technique to ensure that your tests are testing your code or how much of your code you exercised by running the test.
What Test Coverage does?
  • Finding the area of a requirement not implemented by a set of test cases
  • Helps to create additional test cases to increase coverage
  • Identifying a quantitative measure of test coverage, which is an indirect method for quality check
  • Identifying meaningless test cases that do not increase coverage
Advantages of Test Coverage
  • It can assure the quality of the test
  • It can help identify what portions of the code were actually touched for the release or fix
  • It can help to determine the paths in your application that were not tested
  • Time, scope and cost can be kept under control
  • Defect prevention at an early stage of the project lifecycle