Test Design

In software engineering, test design is the activity of deriving and specifying test cases from test conditions to test software.

Test Scenario: High level functionality of the user story / Application

Test Cases are usually derived from test scenarios with Test Steps and Expected Result. Making Test Plan document has multiple benefits. Help people outside the test team such as developers, business managers, customers understand the details of testing. Test Plan guides our thinking. It is like a rule book, which needs to be followed.

Test Suite (Set): A set of test scripts or test procedures to be executed in a specific test run.

Details which we need to include while creating a test design using Excel sheet.

Test Case ID - A unique identifier of the test case.

Test Summary - One-liner summary of the test case.

Description - Detailed description of the test case.

Prerequisite or pre-condition - A set of prerequisites that must be followed before executing the test steps.

Test Steps - Detailed steps for performing the test case.

Expected result - The expected result in order to pass the test.

Actual result - The actual result after executing the test steps.

Test Result - Pass/Fail status of the test execution.

Automation Status - Identifier of automation - whether the application is automated or not.

Date - The test execution date.

Executed by - Name of the person executing the test case.

Sample Test Case for Salesforce Login functionality: 

What are the differences between test scenario, testcase and a test script?

Test Scenario is a one-line statement that explains what you need to test. It does not explain about How it needs to be tested. First, as an ideal case you should design test scenarios, get it reviewed and approved.

Test scenario designing takes less time but more analysis of user requirements.

Test Case focuses on 'how to' situation. It is mostly detailed step by step instruction that tells you how to interact with the system in order to execute the test.

Testcases can be executed by anyone in the team because of their simplicity and user friendliness.

Testcases takes more time because you are writing steps focusing the test scenario on consideration.

Test Script is a term use in automation testing. When your test is automated, you call it as a test script.

Use Case V/s Test Case

a. Use Case: Describes functional requirement, prepared by Business Analyst (BA).
b. Test Case: Describes Test Steps/Procedure, prepared by Testers.

Test Scenario V/s Test Case

a. Test Scenario is "What to be tested" and Test Case is "How to be tested".

Test Suite (Test Bed):

a. Test Suite is a group of test cases that belong to the same category.