my question is... if you take a manual test case and automate it... do you still need to run it manually?
if so then why automate it :) And if it is automated why does it need to be with the manual test cases? how will you know what is automated or not? probably a flag somewhere its always a flag also, By good description of what it is doing I hope you mean something in more of a declarative scenario. On Thu, Sep 19, 2013 at 3:30 PM, Dan <[email protected]> wrote: > So we're standing up ALM now actually, which has the rest API, but I'm not > sure I want to go down that road. One thing that's really drawing me to > cucumber is that along with reporting the results of the test you get a > good description of what it's doing. It is possible to pull the > information from QC via the api and commit other sorts of information back > to QC. If I do that though I lose the coupling between gerkins and > cucumber and the rest of the framework it seems. > > Dan > > > On Thursday, September 19, 2013 3:15:29 PM UTC-4, johnssn wrote: > >> At my previous company we were using TestLink and Test::Unit. I modified >> Test::Unit to update tests as they were executed (individual classes or >> methods just needed to include the test id as part of the class or method >> name). The test would make a call to TestLink as each test result was >> obtained. >> >> A better way of doing it might be to let the test run to completion and >> then have a post-processing step that parses the results using regular >> expressions and then does the update. The advantage to this is if you get a >> really bad run you don't care about you can just reprocess the results from >> the previous run. If you care about that. >> >> It does look like QC has an API that allows updates. You just need to >> make sure whatever ID QC is using gets into the results somehow, then use >> that. >> >> It looks like the latest version has a rest api (yay!). Here's the link >> to that API doc (down at the bottom of the thread) >> >> http://h30499.www3.hp.com/t5/**Quality-Center-Support-and-** >> News/ALM-11-0-REST-API-**reference-guide/td-p/4747218#.**UjtMubyraIs<http://h30499.www3.hp.com/t5/Quality-Center-Support-and-News/ALM-11-0-REST-API-reference-guide/td-p/4747218#.UjtMubyraIs> >> >> >> ------------------------------ >> *From:* Dan <[email protected]> >> *To:* [email protected] >> *Sent:* Thursday, September 19, 2013 11:42 AM >> *Subject:* Re: [wtr-general] Cucumber and Quality Center >> >> I should clarify. QC won't be going away. It's going to remain the >> repository for manual test cases from which we'll create automation. We >> use watir-webdriver as opposed to QTP in the cases where our tests are >> browser based. My concern is that if we have the test cases in QC and then >> we create automated watir test cases using cucumber, that we now >> essentially have two test cases that need to be maintained. I'm trying to >> think of a more intelligent way for them to work together. >> >> Dan >> >> On Thursday, September 19, 2013 1:39:02 PM UTC-4, Oscar.Rieken wrote: >> >> If you are going to migrate over to cucumber from QTP. I have done that >> they way we did it was located the important behaviors that were being >> tested in QTP rewrite them in cucumber/watir and then delete them from QTP. >> >> >> >> On Thu, Sep 19, 2013 at 11:50 AM, Dan <[email protected]> wrote: >> >> I'm not sure that this is the correct forum for this, but I'm sure that >> someone here must have run into a similar situation. We pretty heavily use >> QC/ALM here along with a mixture of QTP and watir-webdriver. Currently >> we're using a custom framework, but I'd like to start moving to something >> like cucumber, since there's a lot of advantages there. The problem is >> using cucumber seems like a duplication of what we're doing in Quality >> Center. Any thoughts on this would be greatly appreciated. >> -- >> -- >> Before posting, please read http://watir.com/support. In short: search >> before you ask, be nice. >> >> [email protected] >> http://groups.google.com/ >> group/watir-general<http://groups.google.com/group/watir-general> >> watir-genera...@ googlegroups.com >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Watir General" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to watir-genera...@ googlegroups.com. >> For more options, visit https://groups.google.com/ >> groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> -- >> -- >> Before posting, please read http://watir.com/support. In short: search >> before you ask, be nice. >> >> [email protected] >> http://groups.google.com/**group/watir-general<http://groups.google.com/group/watir-general> >> watir-genera...@**googlegroups.com >> >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Watir General" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to watir-genera...@**googlegroups.com. >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> -- > -- > Before posting, please read http://watir.com/support. In short: search > before you ask, be nice. > > [email protected] > http://groups.google.com/group/watir-general > [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "Watir General" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
