Fixing the "Fake Pass" Issue in Test Execution

Issue Summary: The "Fake Pass" issue occurs when a keyword does not perform the intended action during test execution, but the test report still shows the step as passed. This can lead to inaccurate results and potential failures in actual workflows.

Solution:

1. Check Execution Screenshots:

   • Always review the screenshots associated with each test step in the execution report. Analyze them carefully to ensure that the expected actions were actually performed. 
     
     
     
   • For instance, if the "Type By Text" keyword was supposed to enter "John" into the username field, verify this in the screenshot. If the text wasn’t entered but the report shows a pass, it indicates a fake pass.
     
     
     

2. Review Connected Steps:

   • Inspect any failed steps in the test case. Each test step is usually connected to the next. If a step with correct input and output parameters fails, it may be due to a previous step that was a fake pass. Check the preceding step to confirm whether it executed correctly or if it’s responsible for the failure.

3. Investigate Potential Causes:

   • This issue might be caused by a plugin problem or any internal bug that may be related to test application. To resolve it, contact the Opkey Support team. They can assist in investigating the root cause and provide a fix to prevent further occurrences.
     
     
     For further info on debugging of test cases, click here