Skip to Content

Changes for page Acceptance Tests

Last modified by chrisby on 2024/05/11 08:20
From version 2.14
edited by chrisby
on 2023/12/07 22:02
Change comment: There is no comment for this version
To version 2.15
edited by chrisby
on 2024/03/03 14:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,19 +14,17 @@
14 14  
15 15  Below is the business acceptance test code of a "Login Scenario" written in the "Gherkin" language, which is used, for example, by the Cucumber acceptance testing framework:
16 16  
17 -```cucumber
18 -Feature: User Login
19 - In order to access my account
20 - As a user
21 - I want to be able to log in using my credentials
17 + Feature: User Login
18 + In order to access my account
19 + As a user
20 + I want to be able to log in using my credentials
21 +
22 + Scenario: Successful login
23 + Given I am on the login page
24 + When I enter a valid username and password
25 + And I click the login button
26 + Then I should see my dashboard
22 22  
23 - Scenario: Successful login
24 - Given I am on the login page
25 - When I enter a valid username and password
26 - And I click the login button
27 - Then I should see my dashboard
28 -```
29 -
30 30  * **Ease of Comprehension**: As shown above, the technical keywords in business test code are replaced with easy-to-understand ones that allow business people to read and write executable tests. Business acceptance test code should always be available to stakeholders.
31 31  
32 32  ### Tester Roles