---恢复内容开始---

1. test case: how to test --如何测试

test scenario: what to  be tested  --测试什么

2. test scenario contain many test cases  -- 测试场景可以包含很多的测试用例

example:

Requirement is to test your phone WiFi:

test scenario: verify the device automatically connect to wi-fi if user create new profile

test case: create wifi and verify that it create created successfully

verify that device is able to connect to wifi.

3. detaild differencesDifference between Test cases vs Test scenarios:

Test Case	Test Scenario
Test case consist of test case name, Precondition, steps / input condition, expected result.	Test scenario consists of a detailed test procedure. We can also say that a test scenario has many test cases associated with it. Before executing the test scenario we need to think of test cases for each scenario.
Test cases are low level actions and it can be derived from test scenarios.	Test scenarios are the high level classification of test requirement grouped depending on the functionality of a module and it can be derived from use cases.
Test case is give detailed information about if any pre-condition, what to test, how to test and expected result etc.	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.	Test Scenario means talking and thinking requirements in detail.
Test cases are set of steps which performed on system to verify the expected output.	Test scenario is thread of operations.
Test cases are more importance in case where development is happening onsite and QA is happening Off shored. It will help to understand and make both developer and QA in sync.	Test scenarios are more important when time to write test cases is no sufficient and team members are agree with the detailed one liner scenario.
Writing test cases is one time effort which can be used in future while executing regression test case. While reporting defects it will help tester to link the defect with test case id.	In new software testing generation it is new idea and time saver activity. The addition and modification (easy maintainability) of test scenarios is easy and independent on specific person.
The detailed test case document is full proof guard for new software tester. If developer missed something then it is easy to catch while executing these full-proof test cases.	One of the most positive point about test scenario is good test scenarios reduces the complexity and repeatability of product.
It requires more time and resources due to detailed test case which talks about how to test and what to test.	If the test scenario not detailed enough then it might take some time to discussion and understand what test scenario is exactly talking about.