Re: Case Conductor requirements

2011-12-13 Thread Javier Domingo
Very interesting and enjoying platform, I would improve going backward function a little more, as if done in js doesn't store the previous state. Its quite smart thought, Javier Domingo 2011/12/13 Alex Lourie djay...@gmail.com On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez

Re: Case Conductor requirements

2011-12-13 Thread Alex Lourie
On Tue, Dec 13, 2011 at 11:05 AM, Javier Domingo javier...@gmail.comwrote: Very interesting and enjoying platform, I would improve going backward function a little more, as if done in js doesn't store the previous state. Its quite smart thought, Javier Domingo Javier You can look at the

Re: Case Conductor requirements

2011-12-12 Thread Alex Lourie
On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez gema.gomez-sol...@canonical.com wrote: Hi QA team, I am not sure if you have all heard, but just in case. Litmus seems to be about to be substituted by a new tool the QA Mozilla team are developing. The new tool is called Case Conductor.

Re: Case Conductor requirements

2011-12-12 Thread Vadim Rutkovsky
I'd also like import/export functionality (in plain text, at least) and some API for advanced reporting 2011/12/13 Alex Lourie djay...@gmail.com: How about test cases versioning? What is the test case needs fixing? Agree with Alex, however we may cope with it using tags (e.g. 'stable',

Re: Case Conductor requirements

2011-12-12 Thread Alex Lourie
On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez gema.gomez-sol...@canonical.com wrote: Hi QA team, I am not sure if you have all heard, but just in case. Litmus seems to be about to be substituted by a new tool the QA Mozilla team are developing. The new tool is called Case Conductor.