|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation speci... Otto Diesel (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... Otto Diesel (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... Otto Diesel (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... tizki ko (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-952) Documentation ... Otto Diesel (JIRA)
In our company we have technical test automaters and non-technical testers. The testers are strong at business logic and test design, but very weak at technical stuff like programming.
The JBehave documentation on www.jbehave.org seems to be written for people with programming skills or for the people who write the step implementations.
It is hard for a tester with no programming skills to learn writing JBehave stories by using the documentation on www.jbehave.org since it is not written for people like him.
We have to explain to testers how to write JBehave stories. It would be easier for us if we could tell them: "Read the tutorial on the JBehave site". But there is no such tutorial written for people like them (non-programmers).
JBehave enables separation of coding and test design. There are teams where testers have no programming skills. They need a documentation about how to write stories which is written in such a way that they understand it easily.
I am still a bit of a JBehave learner. But I am willing to contribute such a Wiki page or tutorial for non-programmers on how to write stories. As it seems I have to clone the repository, commit my proposals and link it to this issue.