Sei sulla pagina 1di 5

Setting up for automation

Mac Users -
1. Download and Install Ruby latest version ( I did 2.0, please
do the latest)
http://net.tutsplus.com/tutorials/ruby/how-to-install-ruby-on-
a-mac/
Follow all the steps in this document from 1 to 4 and it will
install RVM and Xcode also
Note : XCODE comes free from Apple store so you can
install from there.
2. In terminal make sure to run - $ ruby -v to check the version
of ruby installed.
3. Mac : Install Bundler by writing in commandline $ gem
install bundler
4. Git download and configure git :
https://help.github.com/articles/set-up-git

Windows Users -
1. Ruby can be installed from this link.
https://www.ruby-lang.org/en/downloads/
2. RVM, Ruby Gems ,Bundle install
http://precessionmedia.com/blog/install-and-run-rvm-
bundler-windows-drupal-omega-4-specific

3. In terminal make sure to run - $ ruby -v to check the version
of ruby installed.


5. Install git bash - https://openhatch.org/missions/windows-
setup/install-git-bash

6. Install Bundler by writing in git bash $ gem install
bundler

7. Git download and configure git :
https://help.github.com/articles/set-up-git


After setting up your machine for automation ,clone the
repository in Git
1. You should create an account in github create one if you
dont have any.
https://github.com/
2. Ask Angel from Ops team to provide you access to SSI-
Organization. You will need to give him your github id
created in step 1.
3. Create your own repository in Git.
4. Once you have been added to SSI-Organization , you will
need to clone from terminal/git bash. For that go to the
folder you want the repository to be cloned and then -
$ git clone https://github.com/SSI-Avalon/QA.git
5. Check to see if you see the files in directory .
6. Yes I see files Congratulations you are all set to run the
automation.

To run the automation
1. Go to QA directory from terminal/git bash
2. In the QA directory run the following command s to setup
the environment variables
i) TEST_ENV = config, or config-t2, whatever the
host name is.
ii) DATASET = the tenant
iii) GOOGLEDRIVEPWD = password you use for
google drive
iv) USERNAME = username for google drive, for
example mine is arvohra@servicesource.com
v) SPREADSHEET_KEY = the key is in the url of the
google doc, for
example 0Amt5uhVRpMQOdDFCRERKYlpKRUxjZ
WN0cy1HeGk0X3c is in the
url https://docs.google.com/a/servicesource.com/sp
readsheet/ccc?key=0Amt5uhVRpMQOdDFCRERK
YlpKRUxjZWN0cy1HeGk0X3c#gid=8
3. Run this command in order to run the tests for navigation
tab from the new configuration guide (run within QA dir )
QA > rspec config_spec/config/navigation_spec.rb -f d -
c

Similarly you can run tests for all the tabs by replacing
navigation_spec.rb to whatever you want to test.



Automation has been stable to
1. navigation_spec.rb
2. search_facet_spec.rb
3. relationships_spec.rb
4. grid_columns_spec.rb
5. filters_spec.rb
6. attributes_spec.rb

We still need to work on
1. test_spec.rb
2.actions_spec.rb
3. Exception handling to error out gracefully is something need to
be worked on.

Note :
1. Automation only runs on new configuration guide and the
spreadsheet should have all column headers starting from row
number one.
2. Also all the roles mentioned should be setup in the
environment we are testing.
3.There should be no rough data in the worksheet because it will
try to run those against the tenant and environment and then it
will fail there only since we need to work more on exception
handling.

Potrebbero piacerti anche