Tutorial_eng
To log in to Seed-Test you either need a Seed-Test account or you can log in with your Github account.
To create a Seed-Test account, click on "Register here". Alternatively, you can also use a demo version without registration under "Try Our Demo".
As soon as you logged in successfully via GitHub you can select the project you want to use from the appearing list of GitHub-Projects. When logging in with a Seed-Test account, a New Custom Project must first be created in the Account Settings.
You can change the project selection at any time on the upper left navigation bar under "Projects".
Using the account management, you can also connect your seed-test account with a Github or Jira account. So you can also view and use the projects created there. Alternatively, you can also create a custom repository, here you do not need a Github or Jira account.
Before you can work with Seed-Test in connection with GitHub or Jira, you need to create an issue in your GitHub repository / Jira project and assign it the label "story", which you may need to create beforehand. In Jira this process is analogous, here the label "Seed-Test" must be set.
Once you have fully configured your issues, multiple scenarios can be created in Seed-Test. To do this, you can unfold a list of scenarios for each story in the sidebar. If no scenario exists yet, you can create a new scenario by pressing the "+" button in the scenario view.
You can edit the title ("Pen"-Button next to the scenarios name), change the background of the story (-> explanation in chapter "Advanced") and most important: edit/fill the Given/When/Then-Elements. Each Given/When/Then-Element has multiple options to configure it. You can find them by clicking the "+"-Button on the far right side of each element. As soon as you click the button, a small window appear beneath the button, which provides you with different selection options. In addition, you can select single or multiple steps in the action bar, copy and paste them to the clipboard, deactivate them or save them as a block (-> explanation in chapter "Advanced")
The following list is supposed to give you explanations of the individual elements, a list of all the selection options and examples on how they look like:
-
Given:
-
Indicates an Pre-Condition
-
Options: Role/Website
-
Examples: “As a XY”, “I am on the website: XY”
-
-
When:
-
Indicates a Action
-
Options: Website/Button/Field/Radio/Dropdown/HoverOverAndSelect/Checkbox
-
Examples: “I go to the Website: XY”, “I click the button: XY”
-
-
Then:
-
Indicates a Post-Condition / Result
-
Options: Website/Text
-
Examples: “So I will be navigated to the website: XY”, “So I can see the text XY in the textbox: XY”
-
Once you have created all items and filled them in correctly, you can save the changes by clicking on the disk icon.
Since you now have created a scenario, you can perform tests for it. You can do that by clicking the "Run Scenario"-Button, which you can find directly beneath the "Example"-Panel. As soon as you press the button tests using your set specifications (given/when/then) will be carried out. As soon as all steps are finished, the results will be shown to you in an overview.
In the report, by expanding the "Feature" and "Scenario" sections, you can view the status of each step, its duration, any error messages and screenshots.
Next to the "Run Scenario"-Button there will now be two other buttons you can click, the "Arrow"-Button, which you can use to close the "Test Result"-Panel and open it up again, and the "Download"-Button, which you can use to download the test results in HTML-format.
Furthermore, you have the opportunity to run a story (with multiple scenarios) as a whole. Therefore you can use the "Run Story"-Button in the upper story area. This works the same as testing a single scenario. You can now find a list of all tested scenarios with its scenarios in the "Feature"-Panel and examine each one for error messages. You can download these results by using the "Download"-Button, too.
In this chapter you can find useful actions you can use in addition to the main actions.
-
Background:
-
You can use the background to set actions, which will be carried out before testing the whole story. This happens before the test runs through the Given/When/Then-Steps and is used across all scenarios. In short: A background allows to set Given-Steps used for all scenarios.
-
Example:
-
-
Examples:
-
For using examples, you have to create placeholders in your Given/When/Then-Steps. You can assign values to the placeholders, which will be used instead of them. You can assign more than one value. If there is more than one value assigned, the whole test will be run as often as there is a value that hasn't been used once. Each test case created by this will be carried out individually and independent.
-
Example:
-
-
Actionbar:
-
The action bar allows you to select steps, deactivate them, copy them to the clipboard and combine them as a block. For saving the steps as a block a mask opens where you can name the block.
-
Example:
-
This block is then visible and usable for everyone assigned to the respective project. You can then use the block or the steps in the clipboard as you like in other stories.
In this chapter you can find useful links for solving upcoming problems.