# UI verifications

**THIS HAS BEEN DEPRECATED AND IS KEPT FOR HISTORICAL INSIGHTS**
**IF UI VERIFICATIONS ARE NEEDED TALK TO #QA_AUTOMATION CHANNEL**

## Prerequisites

0. a relatively recent Ruby version
0. ssh access to box hosting Workstation app configs

## Usage

```
$ bundle install
$ bundle exec rake test PERIOD=196
```

## Testing locally using a real browser

The test suite uses phantomjs (automatically downloading the binary if it's not in PATH). To test locally using a real browser, e.g. when prototyping new tests, use this one-liner:

```
$ rake features BROWSER=chrome PERIOD=196
```

## Jenkins

Configure Jenkins to [build with parameters](https://wiki.jenkins-ci.org/display/JENKINS/Build+With+Parameters+Plugin), requiring the env var PERIOD to be set. In the project config, execute the following shell commands:

```
#!/bin/bash -l
bundle install --without development
bundle exec rake test
```

I have set up a Jenkins project on [jeeves03](http://jeeves03.theorchard.com:8080/job/accounting-run-atf/) to validate this build as I develop it.

## Current issues (as of 6/10/15)

0. QA redis needs to be flushed, otherwise we will see cached data and all the UI tests will probably fail.

0. There is no indicator in the UI for quarterly labels that a new month has been processed, unless the new month is part of a new quarter (e.g. the month of April was processed, so the `accounting_start=` and `&accounting_end=` query params show the new months corresponding to Q2, instead of Q1)

0. There is no dedicated consumer machine on QA for Statement request queued messages. This results in reports not being downloadable.