Changes between Version 1 and Version 2 of GoogleCodeInTaskTestRun


Ignore:
Timestamp:
Nov 9, 2017, 4:43:32 AM (7 years ago)
Author:
richienyhus
Comment:

Add further details

Legend:

Unmodified
Added
Removed
Modified

  • GoogleCodeInTaskTestRun

    v1 v2  
    1818* The ''expected results'' or ''expected outcome'' is what is actually ment to happen at the end of the feature test.
    1919* Together these form a ''test case'', which when grouped together is a ''test plan''.
     20
     21=== Example test case on LeanTesting ===
     22[[Image(leantesting.jpg, 900px)]]
     23
     24Interacting with the Test Case:
     25
     26* Clicking on the arrow in the far-top-right will show or hide the details of the test case
     27* Clicking on "Report Bug" will allow you to report something that you think is a bug or regression
     28* Clicking on "Result" will allow to report the outcome of the test
     29* The four lines or 'hamburger' sign shows that there multiple steps if it is highlighted in blue
     30* Clicking on the paperclip allows you to add an attachment such as a screenshot of a test in progress
     31* Clicking in the text box allows you to comment on the results of the test
     32* Clacking on the "ℹMarkdown styling is allowed" teaches you [https://www.markdowntutorial.com how to use markdown]
     33
     34=== The four results ===
     35
     36The following are the for available results that you can choose from:
     37
     38* ✔ : Pass - You were able to successfully complete this test case without problems
     39* ❌ : Fail - The outcome was different to the expected result
     40* CNT : Could Not Test - The test itself was outdated or otherwise in error
     41* N/A : Not Applicable - The feature or function is not available to be tested on your system