StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POrequire to execute a script in between a test case
text
Body
copied!<p>I have a scenario where, I have a RoR application, mysql, and there is a workflow, where</p> <ul> <li>end user will follow that workflow, and register her software</li> <li>software is local to end user, running on her machine </li> <li>in between this workflow, I make a http request to this software and it responds back</li> <li>this hand shaking take place between rails app and that software</li> <li>updating a couple of entries in db</li> <li>and now I have to write a test case for this</li> <li>that after this workflow done, <ul> <li>proper entries are been added to db</li> <li>checking whether workflow is executed successfully</li> <li>plus hand shaking took place well, so a complete cycle </li> </ul></li> <li>And Am looking for a best approach here to go with</li> </ul> <p>For now, we do not have prepared, or planning for a nice way of testing entire app here, but just preparing a few important test cases only. And this one is the first one of this kind. So far we were doing it manually.</p> <p>Now being lazy, we want to automate this, and I am thinking of using watir. I have a software simulator for hand shaking, I could execute that simulator in watir and get this whole cycle tested.</p> <p>Does this sound good that my watir/rb script is </p> <ul> <li>executing a script</li> <li>checking db status</li> <li>executing workflow</li> <li>stopping that script</li> <li>checking for db status</li> </ul> <p>But obvious all ruby/rails units involved here would have their own unit test cases prepared apart, but I am interested in testing this whole cycle.</p> <p>Any better suggestions, comments?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload