Skip to content
Browse files

few typos found during french translation ....

  • Loading branch information...
1 parent a64ef45 commit efdad70c0edac7f59e40aa7f733319f2d6a719e1 @poum poum committed Mar 13, 2012
Showing with 4 additions and 4 deletions.
  1. +4 −4 thucydides.doc
View
8 thucydides.doc
@@ -1397,7 +1397,7 @@ public class NewCompanyPage extends PageObject {
When writing acceptance tests, you often find yourself expressing expectations about individual domain objects or collections of domain objects. For example, if you are testing a multi-criteria search feature, you will want to know that the application finds the records you expected. You might be able to do this in a very precise manner (for example, knowing exactly what field values you expect), or you might want to make your tests more flexible by expressing the ranges of values that would be acceptable. Thucydides provides a few features that make it easier to write acceptance tests for this sort of case.
-In the rest of this section, we will study some examples based on tests for the Maven Central search site (see <<>>). This site lets you search the Maven repository for Maven artifacts, and view the details of a particular artifact.
+In the rest of this section, we will study some examples based on tests for the Maven Central search site (see <<maven-search-report>>). This site lets you search the Maven repository for Maven artifacts, and view the details of a particular artifact.
[[maven-search-report]]
.The results page for the Maven Central search page
@@ -1996,7 +1996,7 @@ Thucydides also provides special support for the Atlassian JIRA issue tracking t
org.apache.maven.pluginsmaven-surefire-plugin2.7.1http://my.jira.server
------------------
-You need to provide the issue number. You can place this in the test title, prefixed by the '#' character. For easyb tests, this just means mentioning the issue number (always starting with a '#' character) somewhere in the scenario name. For JUnit tests, you use the @Title annotation as shown here:
+You need to provide the issue number. You can place this in the test title, prefixed by the # character. For easyb tests, this just means mentioning the issue number (always starting with a # character) somewhere in the scenario name. For JUnit tests, you use the @Title annotation as shown here:
[source,java]
------------------
@@ -2070,7 +2070,7 @@ If a test needs to be associated with several issues, you can use the @Issues an
[source,java]
------------------
-@Issues({"#123", #456"})
+@Issues({"#123", "#456"})
@Test public void shopping_cart_should_let_users_add_multiple_articles() {
steps.add_item_to_cart("nuts"); steps.add_item_to_cart("bolts");
steps.cart_should_contain("nuts","bolts");
@@ -2079,7 +2079,7 @@ If a test needs to be associated with several issues, you can use the @Issues an
When you do this, issues will appear in the Thucydides reports with a hyperlink to the corresponding issue in your issue tracking system.
-jira-integration-example
+
=== Bi-directional JIRA integration

0 comments on commit efdad70

Please sign in to comment.
Something went wrong with that request. Please try again.