Getting Started with qTest Scenario
Now that you have installed qTest Scenario, let’s walk through a quick set up video to get you started on your BDD journey. For this example, we will be using the Coffee Shop Jira project. Select the project setting and then chose qTest Scenario in the left panel to start configuration.
There are two sections under project settings tab:
In this video we will be focused on qTest Scenario but in other videos we will show how to connect qTest Scenario with qTest Pulse enterprise BDD.
Now click Click Configure your project
qTest Scenario integrates directly with your source code repositories, like GitHub and Bitbucket, to store your feature files. In this example, we will be using GitHub. If you don’t have a current BDD project set up, you can clone one of our demo repositories on the QASymphony GitHub page to one of your own GitHub teams.
I’ve cloned this project into my qasryan/coffee-shop repository, so we will be using this for the example demonstration. Add the repo location, and where you feature files will be stored. If using private repositories, make sure you check out the advanced setting to configured. Next, select your default branch where you will store and sync existing features files with qTest Scenario, in this example Master is our default branch.
For each project, you can select which issue types you will allow users to create features and scenarios. In this example, I’m only going to create features/scenarios with User Stories. Once your setting are saved, we are ready to start collaborating around feature and scenario creation in jira.
Lets create a quick use story to show where the qTest Scenario Add-on will be located. Once you navigate to qTest Scenario editor, you will need to login using your GitHub credentials and select an editor theme.
If you have existing features in your source repository, we can instantly link them using the search feature. Search will pull in all features and scan from your file location that match search terms.
If you want to copy contents from an existing feature, select the copy button and then change the feature file name. Once saved Scenario will create a brand new feature file in your GitHub repository.
qTest Scenario helps facilitate better collaboration and standardization. Being able to autocomplete tags makes sure your features our organized correctly. Auto completion a thae step level allows for better reuse of previously implemented steps. And syntax checking and error handling directly in Jira keeps teams from making mistakes.
If a developer or engineer needs to refactor the feature file your source code, don’t worry about manually updating the file in Jira. qTest Scenario’s integration will always keep files in sync with any updates.
And if you are looking to scale your BDD processes across your organization, contact QASymphony today on how qTest Scenario Combined with qTest Pulse can enable your teams for enterprise BDD.
Be sure to contact QASymphony on how we can help you scale your BDD processes with qTest Pulse.