Skip to end of metadata
Go to start of metadata
  • No labels

1 Comment

  1.                                                 KPME QA  Set Up Guide v1

     

    This page would provide information of software and framework setup for AFTs.

    Software Requirements :

    1.ruby 1.9.3p545

    2.Ruby Mine 6.3 +sub version 1.6

    3. ruby development kit (only for Windows. Mac and Ubuntu does not require dev kit)

    4. Firefox version 27.0

    Installation and Configuration :

    1. Download and install ruby.
    2. Download Rubymine IDE, extract (if needed) and provide license information that is available on the wiki. Note that you will need a signed CLA attached to your KIS profile to access the license information.
    3. Install ruby development kit.Provide the rdk path in the PATH environment variable.
    4. Download Firefox version 27 and install
    5. Once installed checkout the AFT code in ruby mine from the svn path (VCS-> subversion) from the menu bar


       https://svn.kuali.org/repos/kpme/branches/dev/khr-automated-functional-tests
    6. Once checked-out,  Rubymine will automatically detect missing gems on the project and request a download.     
    7. Click install missing gems.
    8. Do not enter any parameters for bundle install, just hit ok.

     

    Structure of code :

    There are four important components in the AFT. They are

    1. Feature file – This  is written in simple language and is the business representation of the test case. The feature files are written and saved inside the features folder. Every feature file scenario would have a GIVEN,WHEN and THEN statement.

    2. Step definition – The feature files are then converted into step definitions.The skeleton can be generated for every above statement.This is saved under the step definition folder.

    3. Page object—This file has the  required objects and page elements defined. This corresponds to a one to one mapping with the web page and is saved in the pages folder.

    4. Data object – This is the file which has the business logic and actions to be performed with the page elements and is saved under the data object folder under the lib.

       env.rb – This file has the environment and browser instatiation details and is inside the support folder. The variable for changing the test site is $test_site (approx in line # 5 in        env.rb)
       Sample videos : https://wiki.kuali.org/display/STUDENTDOC/QA+Training+Fall+2013


    Execution of  AFT:

    Once the files have been successfully created they can be executed in from the feature file.  Every scenario can be run separately or a complete feature file can be executed. To execute a single scenario right click on the “Scenario” and click run. To execute a complete feature file right click on the feature file and then run it. The results can be observed in the result window and any mismatches from the THEN statement would be shown as error.

    To execute only a single scenario :

    Right click on the scenario name in the feature file and the below pop up shows up and click Run

     

     

    To execute a complete feature file :

    Right click on the feature file and below pop up shows up and click Run