|
77 | 77 | </div> |
78 | 78 | <divclass="col"> |
79 | 79 | <preclass="highlight"><spanclass="gh">*** Settings ***</span><spanclass="p"></span> |
80 | | -<spanclass="kn">Library</span><spanclass="p"> </span><spanclass="nn">Selenium2Library</span><spanclass="p"></span> |
| 80 | +<spanclass="kn">Library</span><spanclass="p"> </span><spanclass="nn">SeleniumLibrary</span><spanclass="p"></span> |
81 | 81 |
|
82 | 82 | <spanclass="gh">*** Variables ***</span><spanclass="p"></span> |
83 | 83 | <spanclass="p">${</span><spanclass="nv">SERVER</span><spanclass="p">} </span><spanclass="s">localhost:7272</span><spanclass="p"></span> |
@@ -235,15 +235,15 @@ export default { |
235 | 235 | items: [ |
236 | 236 | { |
237 | 237 | text: |
238 | | -'<p> Let\'s start with a real-life example from our <a href="https://bitbucket.org/robotframework/webdemo">web demo project</a>. Here we have a test suite with one test case which tests that login is valid. As you can see, test data syntax is based on <span>keywords</span>. </p> <p> Keywords are composable, meaning you can define new keywords that use pre-existing keywords. This way, you can abstract details of testing to something that makes immediate sense; for example, we don\'t need to know what exactly the step <span>Submit Credentials</span> actually does, unless we want to. Test cases are therefore clear and readable, with just the right level of abstraction to convey the <span>intent</span> of the test, rather than the nuts and bolts. </p> <p> See next example for what you\'re going to get once this example is run! </p>' |
| 238 | +'<p> Let\'s start with a real-life example from our <a href="https://github.com/robotframework/WebDemo">web demo project</a>. Here we have a test suite with one test case which tests that login is valid. As you can see, test data syntax is based on <span>keywords</span>. </p> <p> Keywords are composable, meaning you can define new keywords that use pre-existing keywords. This way, you can abstract details of testing to something that makes immediate sense; for example, we don\'t need to know what exactly the step <span>Submit Credentials</span> actually does, unless we want to. Test cases are therefore clear and readable, with just the right level of abstraction to convey the <span>intent</span> of the test, rather than the nuts and bolts. </p> <p> See next example for what you\'re going to get once this example is run! </p>' |
239 | 239 | }, |
240 | 240 | { |
241 | 241 | text: |
242 | | -'<p> Executing the test suite file from previous example, we get the meat and bone of Robot Framework: A comprehensive debriefing on what happened in the test execution in two parts: the <span> Report</span> and the <span>Log</span>. </p> <p>This Report and Log are based on executing the test suite described in the previous example and is from our <a href="https://bitbucket.org/robotframework/webdemo">web demo project</a>.</p><p> Report details clearly viewable statistics including Pass/Fail ratios and elapsed times. This gives you great overview on the test execution. </p> <p> Log details statistics from each step of the test execution, from keyword to keyword. It enables you to drill down on the specifics of the test in case of failure or otherwise. </p>' |
| 242 | +'<p> Executing the test suite file from previous example, we get the meat and bone of Robot Framework: A comprehensive debriefing on what happened in the test execution in two parts: the <span> Report</span> and the <span>Log</span>. </p> <p>This Report and Log are based on executing the test suite described in the previous example and is from our <a href="https://github.com/robotframework/WebDemo">web demo project</a>.</p><p> Report details clearly viewable statistics including Pass/Fail ratios and elapsed times. This gives you great overview on the test execution. </p> <p> Log details statistics from each step of the test execution, from keyword to keyword. It enables you to drill down on the specifics of the test in case of failure or otherwise. </p>' |
243 | 243 | }, |
244 | 244 | { |
245 | 245 | text: |
246 | | -'<div> <p> Keywords can be defined outside of the test suite and be imported as an external resources. This means you can collect generally useful keywords to one place and share them throughout your project, keeping also the testing <a href="http://en.wikipedia.org/wiki/Don\'t_repeat_yourself">DRY</a>! </p> <p> Below, we have test case testing invalid login in <a href="https://bitbucket.org/robotframework/webdemo">our very own web demo</a>. As you can see, we can abstract away a lot of necessary, but ultimately non-expressive nuts and bolts of the testing to the <span>resource file</span>.</p>' |
| 246 | +'<div> <p> Keywords can be defined outside of the test suite and be imported as an external resources. This means you can collect generally useful keywords to one place and share them throughout your project, keeping also the testing <a href="http://en.wikipedia.org/wiki/Don\'t_repeat_yourself">DRY</a>! </p> <p> Below, we have test case testing invalid login in <a href="https://github.com/robotframework/WebDemo">our very own web demo</a>. As you can see, we can abstract away a lot of necessary, but ultimately non-expressive nuts and bolts of the testing to the <span>resource file</span>.</p>' |
247 | 247 | }, |
248 | 248 | { |
249 | 249 | text: |
|