bugtracker typos

This commit is contained in:
Volkan Gezer
2014-05-31 04:09:09 +02:00
parent 69f524a3b7
commit f40136dc0f
2 changed files with 4 additions and 4 deletions

View File

@@ -34,7 +34,7 @@ How will it work?
#. Before a pull request will be merged into master or the corresponding
branch at least 2 reviewers need to give :+1 score.
#. Our `continuous integration server`_ will give an additional indicator for
the quality of the pull rquest.
the quality of the pull request.
Examples
--------

View File

@@ -141,7 +141,7 @@ Why do we have it?
What does a developer think?
"Ill check the Scenario described earlier works as expected. If necessary
Ill update the related Gherkin Scenarios. `Jenkins`_ will test the scenario
on all kinds of platforms, webserver and database combinations with
on all kinds of platforms, web server and database combinations with
`cucumber`_."
When can I pull?
@@ -159,13 +159,13 @@ Why do we have it?
With the Gherkin Scenario from the Concept Phase reviewers have a checklist to
test if a Bug has been solved and if an Enhancement works as expected. **The
most eager reviewer we have is Jenkins**. When it comes to testing he soldiers
on going through the different combinations of platform, webserver and
on going through the different combinations of platform, web server and
database.
What does a developer think?
"Damn! If I had written the Gherkin Scenarios and Cucumber Step Definitions I
could leave the task of testing this on the different combinations of platform,
webserver and database to Jenkins. Ill miss something when doing this
web server and database to Jenkins. Ill miss something when doing this
manually.*
When can I pull?