You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
import TextBlock from "@/Components/TextBlock.vue";
import TextBlock from "@/components/TextBlock.vue";
export default {
components: {
Expand All
@@ -235,15 +235,15 @@ export default {
items: [
{
text:
'<p> Let\'s start with a real-life example from our <a href="https://bitbucket.org/robotframework/webdemo" target="_blank">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 class="italic">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 class="teletype">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 class="italic">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>'
'<p> Let\'s start with a real-life example from our <a href="https://github.com/robotframework/WebDemo" target="_blank">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 class="italic">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 class="teletype">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 class="italic">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>'
},
{
text:
'<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 class="bold"> Report</span> and the <span class="bold">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" target="_blank">web demo project</a>.</p><p id="example-report-last-paragraph"> 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>'
'<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 class="bold"> Report</span> and the <span class="bold">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" target="_blank">web demo project</a>.</p><p id="example-report-last-paragraph"> 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>'
},
{
text:
'<div class="caption margin vertical-content"> <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" class="bold" target="_blank">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 class="italic">resource file</span>.</p>'
'<div class="caption margin vertical-content"> <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" class="bold" target="_blank">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 class="italic">resource file</span>.</p>'
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.