5 steps for successful automation with Hiptest
46
HIPTEST & AUTOMATION
-
Upload
community-manager-hiptest -
Category
Software
-
view
113 -
download
2
Transcript of 5 steps for successful automation with Hiptest
HIPTEST &AUTOMATION
Basics about Hiptest5 steps for a successfulautomationDemo
Basics about Hiptest5 steps for a successfulautomationDemo
WHAT'S HIPTEST ?
Test management in the cloud
BDD framework
WHAT WE BELIEVE INBDD
Refactoring
Continuous integration
OUR PHILOSOPHY FORAUTOMATION
Developers and testers working together
Scenarios
Action words
Glue
Good design lead to good automation
Action words defines your DSL
Action words are implemented and stored with theapplication code
SAMPLE PRESENTATIONNot a vanilla example
Real life use-case
About 200 tests and action words
More than 600 CI builds
Basics about Hiptest5 steps for a successfulautomationDemo
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
STRUCTURING PROJECTScenarios contain only calls to action words
it "Organization update" do load_coffee_machine_project create_organization_named_name("Hiptest") check_organization_name_exists("Hiptest") check_organization_has_count_users("2") remove_user_name_from_organization("john") check_organization_has_count_users("1") add_user_email_to_the_organization("[email protected]") check_organization_has_count_users("2") close_browsersend
STRUCTURING PROJECTTwo type of action words:
high-level: only call other action words
leaf: only contain action/result steps
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
USING HIPTEST-PUBLISHER AS ASERVICE
0:58
USING COMMAND LINE> gem install hiptest-publisher> hiptest-publisher --token=123456 --language=javascript
GETTING A CONFIGURATION FILE
token = '123456789'language=javascriptframework=jasmineoutput_directory = './'
Do not forget to store that in Git/SVN
FETCHING THE CODE
0:51
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
IMPLEMENTING THE ACTION WORDS
Well, that's your job ;)
And again, keep it in Git/SVN
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
CONFIGURING FOR CICreate a dedicated test run
ADD THE SCENARIO TO THE TESTRUN
ROADMAP TO CI INTEGRATION
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
UPDATE CI BUILD CONFIG
Install hiptest-publisher on CI slavegem install hiptest-publisher
Fetch tests before executionhiptest-publisher --tests-only --test-run-id=3054 -c hiptest-publisher.config
Push results after executionhiptest-publisher -c hiptest-publisher.config -p results.xml
OBSERVE THE RESULTS IN THE TESTRUN
START AGAIN
1 - Create scenario
2 - Pull code
3 - Implement
4 - Add scenario to test run5 - Let CI push results
Basics about Hiptest5 steps for a successfulautomationDemo
