Test cases and test scenarios

TEST CASE	TEST SCENARIO
Test case consists of Test case name, Precondition, Test steps, Expected result and Post condition	Test scenario are one liner but it is associated with multiple test cases
Test case guide a user on “how to test”	Test scenario guide a user on “what to test”
Purpose of test case is to validate the test scenario by executing a set of steps	Purpose of test scenario is to test end to end functionality of a software application
Creating test cases is important when working with testers off-site	Creating test scenarios helps you in a time-sensitive situation (especially working in Agile)
Software applications change often. It leads to redesigning the pages and adding new functionalities. It hard to maintain test cases	Test scenarios are easy to maintain due to its high level design
More time consumption compared to test scenarios	Less time consumption compared to test cases
Required more resources to create and execute test cases	Relatively less resources enough to create and test using test scenarios
It helps in exhaustive testing of application	It helps in agile way of testing end to end functionality
Test cases are derived from test scenarios	Test scenarios are derived from use cases
Test cases are low level actions	Test scenarios are high level actions

Test Scenario	Test Case
A test scenario contains high-level documentation which describes an end to end functionality to be tested.	Test cases contain definite test steps, data, expected results for testing all the features of an application.
It focuses on more "what to test" than "how to test".	A complete emphasis on "what to test" and "how to test.".
Test scenarios are a one-liner. So, there is always the possibility of ambiguity during the testing.	Test cases have defined a step, pre-requisites, expected result, etc. Therefore, there is no ambiguity in this process.
Test scenarios are derived from test artifacts like BRS, SRS, etc.	Test case is mostly derived from test scenarios. Multiple Test case can be derived from a single Test Scenario
It helps in an agile way of testing the end to end functionality	It helps in exhaustive testing of an application
Test scenarios are high-level actions.	Test cases are low-level actions.
Comparatively less time and resources are required for creating & testing using scenarios.	More resources are needed for documentation and execution of test cases. Test Cases Test Scenarios What it is => A concept which provides detailed information what to test, steps to be taken and expected result of the same A concept which provides one-line information about what to test. It’s about => It’s more about documenting details. It’s more about thinking and discussing details. Importance => It’s important when testing is off shored and development is onsite. Writing test cases with details will help both dev and QA team in sync. It’s important when time is less and most of the team members can agree / understand the details from one-liner scenario. Advantage => One time documentation of all the test cases is beneficial to track 1000s rounds of regression testing in future. Most of the time, its helpful while bug reporting. Tester just need to give reference of test case ID and does not require mentioning each and every minute detail. A time saver and idea generation activity, preferred by new generation software testing community. Modification and addition is simple and not specific to a person. For a huge project, where group of people know specific modules only, this activity gives a chance to everyone to look into other modules and brain storm and discuss Beneficial to => A full-proof test case document is a life line for new tester. Good test coverage can be achieved by dividing application in test scenarios and it reduces repeatability and complexity of product Disadvantage => Time and money consuming as it requires more resources to detail out everything about what to test and how to test If created by specific person, the reviewer or the other user might not sync the exact idea behind it. Need more discussions and team efforts.