https://github.com/dkniffin/dummy-qa
https://github.com/dkniffin/dummy-qa
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/dkniffin/dummy-qa
- Owner: dkniffin
- Created: 2016-08-23T19:32:18.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-01-03T15:54:05.000Z (over 8 years ago)
- Last Synced: 2025-02-10T07:17:08.702Z (4 months ago)
- Language: Ruby
- Size: 30.3 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Cucumber - QA Automation Template
This repo provides an example setup for Cucumber and QA Automation. You can also go view all of this content here {insert URL to SB wiki article}. Please follow the steps below for the setup process:
1. `git clone project-name`
1. `bundle install`
1. Create new repo in GitHub interface - name it `project-name-qa-automation`
1. Select `Private`
1. Select `Initialize this repository with a README`
1. Select `Ruby` for `.gitignore`
1. Open the project in editor of choice
1. Search for “TODO” - in console type - `grep -r TODO .`
1. Fill in content for TODO sections
1. Change repos origin - `git remote set-url origin `
1. `Git push`
1. Blah
1. Open your first PR - _please see guide below_
With setup now complete, you are ready to begin writing tests once the PR has gone through the standard SB Review process. Wait for the green check on the merge and simply copy the URL and in the `code-reviews` Slack channel, type `/cr https://github.com/smashingboxes/project-name/pull/1`
## Integrating with backend and frontend
At Smashing Boxes, we develop our web apps using a "hybrid" or decoupled approach. What this means is that the backends and frontends of our apps are built separately, in different repos. Because of this, running Cucumber tests is a little more involved.
In order to do proper TDD, we'll want to run our Cucumber when different things happen:
- When a new backend PR is opened
- When a new frontend PR is opened
- When a new QA PR is opened
To accomplish this, we'll need to configure our build system to pull down the backend and frontend, and run them locally.
### Setting up CI for the app
In both the backend and frontend, add the following to `.travis.yml`
````
before:
- bash <(curl -s BEFORE_SCRIPT_URL)
script:
# ...
# Put the Cucumber test last, because it will cd into different directories
- bash <(curl -s TEST_SCRIPT_URL)
````
Be sure to fill in the `BEFORE_SCRIPT_URL` and `TEST_SCRIPT_URL` with links to the raw file on github, such as `https://raw.githubusercontent.com/smashingboxes/cucumber-template/master/bin/test.sh?token=ABmi0AM58zIPAViTZnHB-IwCyfvscNmlks5XsjiTwA%3D%3D`
## PR Guide
Example:
# Why?
- Ensure user login works
# What Changed?
- New test
## Editor Setup
Below are a few add-ons for Atom (if you prefer Atom) that will be beneficial when writing your tests:
- Atom-Beautify
- Auto-Detect-Indentation
- Cucumber
- Language-Gherkin
- Linter-Rubocop
## Folder Structure
When writing your first test, please adhere to the folder structure below for consistency (this structure is already set in the sample repo):
- features
- scenarios
- admin
- user
- steps
- admin
- page_interactions
- user
- support
- helpers
- test_files
NOTE: The `page_interactions` folder has both `clicking.rb` and `viewing.rb` files for general steps that will be reused throughout your tests.
## Running Tests
Running tests is as simple as `bundle exec cucumber` or `bundle exec cucumber features/.feature`. Tests will either be ran against your local environment or against a QA environment as setup in the `endpoint_helper.rb` file.
## Tape Deployment
TBD
## Travis Integration
TBD
## Sauce Labs Integration
TBD