Skip to main content

How test steps and Expected result and actual result should get differ each other and be unique?

Image
By
 Test steps are action-oriented and describe the registration process, the expected result outlines the desired outcomes, and the actual result provides observations on what actually occurred during the execution of the test case. 

 Each section serves a unique purpose and together forms a comprehensive test case. 
Any discrepancies between the expected and actual results can be easily identified and addressed.


Test steps, expected results, and actual results in test cases should be distinct and unique to provide clarity, avoid ambiguity, and facilitate effective communication between testers and other stakeholders. Here are some guidelines on how to make them differ and unique:


Test Steps:


1. Sequential and Clear:

• Test steps should be listed in a sequential and clear manner. 
• Each step should represent a specific action that the tester needs to perform.


2. Action-Oriented:

• Use action-oriented language in test steps. 
• Clearly state what actions the tester should take, such as clicking buttons, entering data, or navigating to specific pages.


3. Specific and Granular: 

• Break down test steps into specific and granular actions. 
• Avoid combining multiple actions within a single step to maintain clarity

Expected Result: 

1. Outcome-Focused:

• Expected results describe the expected outcome or system behaviour after performing the test steps. 
• Focus on the end result rather than the intermediate steps.


2. Align with Requirements: 

• Ensure that the expected results align with the requirements or acceptance criteria. 
• Link expected results to specific functionalities or user stories.

3. Quantifiable and Measurable: 


• Make expected results quantifiable and measurable whenever possible. 
• Use specific values, states, or conditions to clearly define success.

Actual Result: 

1. Observation and Recording:

 • Actual results describe what actually happened when the tester executed the test steps. 
• Record observations without making interpretations or conclusions.

2. Detail Deviations: 

• If there is a deviation from the expected result, provide detailed information about the observed behaviour. 
• Include error messages, unexpected outcomes, or any issues encountered.

3. Include Artifacts:

 • Attach screenshots, logs, or any relevant artifacts to support the actual results.
 • Visual evidence enhances the understanding of the observed behaviour.









 

Comments

Post a Comment

Popular posts from this blog

A Well Comprehensive Test plan for Manual Testing

By
  Scope Definition: Define the scope based on specifications and requirements provided. However, also include exploratory testing to uncover issues that might not be explicitly mentioned in the requirements. Consider factors like usability, accessibility, security, and performance to broaden the scope beyond just functional testing. Considering factors like usability, accessibility, and security in the scope definition is essential for ensuring a comprehensive testing approach that goes beyond functional requirements Test Case Design: Use a combination of traditional methods like boundary value analysis, equivalence partitioning, and decision tables for structured testing. Incorporate exploratory testing techniques to explore the application and identify unexpected behaviour or edge cases. Prioritize test cases based on risk assessment and criticality. can implement the shift-left approach in...
Post a Comment
Read more

Pre conditions and Post conditions in Test Ng.

By
Pre conditions and PostConditions in Test Ng. Vision of Preconditions and Postconditions: 👉 Ensuring Test Isolation: By using preconditions and postconditions, you ensure that each test method is executed in isolation, with a clean and consistent state. 👉Promoting Reusability: Setup and teardown tasks defined in preconditions and postconditions can be reused across multiple test methods, promoting code reuse and reducing redundancy. 👉Maintainability: Clearly defined preconditions and postconditions enhance the maintainability of test code. Changes or additions to the setup and cleanup logic can be made centrally in these annotated methods. TestNG PreConditions and PostConditions flow.   Before Suite (once) Before Test (once for each <test> in the suite) Before Class (once for each class with test methods in the <test> ) Before Method (before each test method) Test method execution After Method (after each test method) After Class (after all test methods in ...
Post a Comment
Read more

Essential of Creating Test plan in Testing

By
  Why Test Plan is Vital Document! Test Planning process and plan itself serve as vehicle for communicating with other members of the project team, tester, Dev, BA, Peer and other stakeholders. This communication allows the test plan to influence the project team and allows the project team to influence the test plan. We can accomplish this Communication through circulation of one or more test plan drafts and through review meeting. E.g.: Please tell me what the plan is for releasing the test items into the test lab for each cycle of test execution E.g.: Please let me know which version of the test tool   will be used for the regression tests of the previous increment. A test plan Document becomes the record of previous discussions and agreements. Test Plan helps us to Manage the change if you are in Agile , have to this as Handy. Ways to write a Test Plan Document. Analyze the Product: Understand the product's objectives, target users, specific...
Post a Comment
Read more