Difference between revisions of "How to test Ontohub"
(Add first text to how-to-test-ontohub page) |
|||
| Line 1: | Line 1: | ||
| − | If you want to test Ontohub, you can use [http://www.seleniumhq.org/ Selenium] (to be exact the Selenium IDE Plugin for Firefox) and the [http://www.test.ontohub.org Ontohub test platform]. With Selenium you can record test on [http://www.test.ontohub.org test.ontohub.org] and translate them with this gem called [https://github.com/ebolloff/featurecorder featurecorder] for us developer. In the readme ([https://github.com/ebolloff/featurecorder featurecorder]) you'll find instructions what to install and how to test Ontohub. | + | If you want to test Ontohub, you can use [http://www.seleniumhq.org/ Selenium] (to be exact the Selenium IDE Plugin for Firefox) and the [http://www.test.ontohub.org Ontohub test platform]. This site is in an similiar status like Ontohub, but it has a few test data for you to play with. May you want to check on some infos about Selenium and Cucumber before you test our site. |
| + | |||
| + | With Selenium you can record test on [http://www.test.ontohub.org test.ontohub.org] and translate them with this gem called [https://github.com/ebolloff/featurecorder featurecorder] for us developer. In the readme ([https://github.com/ebolloff/featurecorder featurecorder]) you'll find instructions what to install and how to test Ontohub. You'll find these instructions also below. | ||
| + | |||
| + | == Installation and Configuration == | ||
| + | |||
| + | The translation gem feaeturecorder is not hosted on rubygems.org, so to install it you need to download it from [https://github.com/ebolloff/featurecorder here] and run ''bundle'' and ''rake install''. | ||
| + | |||
| + | What you need to do next is to install Mozilla Firefox (currently version 39.0), if you haven't yet. After that you need to install the Firefox plugins 'Selenium IDE' (currently version 2.9.0), 'Selenium XML Formatter' (currently version 1.5.1), which allows you to export the recorded test as XML, and 'Selenium IDE Button'(currently version 1.2.0.1) to start Selenium with an easy button click next to your address bar in Firefox. | ||
| + | |||
| + | After that you need to change some options in Selenium. Start Selenium and click on Options -> Options. In the opened window you select the tab 'Locator Builders'. These handle the locators to find your selected elements in your tests. With drag & drop you can arrange the locators like this: | ||
| + | |||
| + | ui | ||
| + | id | ||
| + | link | ||
| + | name | ||
| + | dom:name | ||
| + | xpath:link | ||
| + | xpath:img | ||
| + | xpath:attributes | ||
| + | xpath:idRelative | ||
| + | xpath:href | ||
| + | dom:index | ||
| + | xpath:position | ||
| + | css | ||
| + | |||
| + | Now Selenium will record the elements with the ID, not the css selector because that could be unexcact. | ||
| + | |||
| + | == Recording == | ||
| + | |||
| + | So let's record some tests. Please check in the Ontohub project that the test you want to record doesn't exist already. Also notice, that Selenium will record every input as plaintext, so create a new account with a different password on test.ontohub.org. Start Selenium, go to test.ontohub.org and click the record button. Everything you interact with the site now will be recorded. With a right click you can add commands like assertText or verifyTitle so check, if a expected element is present. Please just use the assert* and verify* commands, because the other ones aren't supported. If you're done just click the record button again and the record will stop. Now you can export the test as XML via File -> Export Test Case As... -> XML Formatter. | ||
| + | |||
| + | == Translation == | ||
| + | |||
| + | Now you can translate your recorded XML tests to Cucumber. With ''featurecorder -h'' you can see the options of this gem. | ||
| + | |||
| + | Usage: | ||
| + | featurecorder [options] <file> | ||
| + | Options: | ||
| + | -s --scenario-name=<scenario> Name of the scenario. | ||
| + | -f --feature-name=<feature> Name of the feature. | ||
| + | -o --output-directory=<dir> Output directory for generated files. | ||
| + | Default is current directory. | ||
| + | -h --help Show this screen. | ||
| + | |||
| + | With the option -s/--scenario-name you can choose the name for the scenario, with -f/--feature-name the name for the feature. -o/--output-directory lets you decide where you want to save the generated files for Cucumber. If you call featurecorder you need to state the XML file. If you're ready, fork the Ontohub project and you can post the files in a pull request. | ||
Latest revision as of 15:22, 4 October 2015
If you want to test Ontohub, you can use Selenium (to be exact the Selenium IDE Plugin for Firefox) and the Ontohub test platform. This site is in an similiar status like Ontohub, but it has a few test data for you to play with. May you want to check on some infos about Selenium and Cucumber before you test our site.
With Selenium you can record test on test.ontohub.org and translate them with this gem called featurecorder for us developer. In the readme (featurecorder) you'll find instructions what to install and how to test Ontohub. You'll find these instructions also below.
Installation and Configuration
The translation gem feaeturecorder is not hosted on rubygems.org, so to install it you need to download it from here and run bundle and rake install.
What you need to do next is to install Mozilla Firefox (currently version 39.0), if you haven't yet. After that you need to install the Firefox plugins 'Selenium IDE' (currently version 2.9.0), 'Selenium XML Formatter' (currently version 1.5.1), which allows you to export the recorded test as XML, and 'Selenium IDE Button'(currently version 1.2.0.1) to start Selenium with an easy button click next to your address bar in Firefox.
After that you need to change some options in Selenium. Start Selenium and click on Options -> Options. In the opened window you select the tab 'Locator Builders'. These handle the locators to find your selected elements in your tests. With drag & drop you can arrange the locators like this:
ui id link name dom:name xpath:link xpath:img xpath:attributes xpath:idRelative xpath:href dom:index xpath:position css
Now Selenium will record the elements with the ID, not the css selector because that could be unexcact.
Recording
So let's record some tests. Please check in the Ontohub project that the test you want to record doesn't exist already. Also notice, that Selenium will record every input as plaintext, so create a new account with a different password on test.ontohub.org. Start Selenium, go to test.ontohub.org and click the record button. Everything you interact with the site now will be recorded. With a right click you can add commands like assertText or verifyTitle so check, if a expected element is present. Please just use the assert* and verify* commands, because the other ones aren't supported. If you're done just click the record button again and the record will stop. Now you can export the test as XML via File -> Export Test Case As... -> XML Formatter.
Translation
Now you can translate your recorded XML tests to Cucumber. With featurecorder -h you can see the options of this gem.
Usage:
featurecorder [options] <file>
Options:
-s --scenario-name=<scenario> Name of the scenario.
-f --feature-name=<feature> Name of the feature.
-o --output-directory=<dir> Output directory for generated files.
Default is current directory.
-h --help Show this screen.
With the option -s/--scenario-name you can choose the name for the scenario, with -f/--feature-name the name for the feature. -o/--output-directory lets you decide where you want to save the generated files for Cucumber. If you call featurecorder you need to state the XML file. If you're ready, fork the Ontohub project and you can post the files in a pull request.
