Help to automate testcase creation and add it HP Quality Center with Python

[John Smith]

Hi ,

Im trying to automate test case creation ( it can be as a file of any type( xml, txt, etc) and after I would like to add it to HPQC .

Could some one please help and give some ideas from where I can start 

- what is the better tool to use for automation test case creation?

- any python modules I can use with HPQC to import created test-cases, file, etc?

Thank you ,

John

[Aslak Hellesøy]

On Tuesday, 10 June 2014 at 21:29, John Smith wrote:

Hi ,

Im trying to automate test case creation

Do you want test cases to be *created* automatically? Based on what?

Cucumber automates the *execution* of test cases (scenarios), but they still have to be created manually, by human beings. Just like code.

Aslak

( it can be as a file of any type( xml, txt, etc) and after I would like to add it to HPQC .

Could some one please help and give some ideas from where I can start 

- what is the better tool to use for automation test case creation?

- any python modules I can use with HPQC to import created test-cases, file, etc?

Thank you ,

John

--
Posting rules: http://cukes.info/posting-rules.html
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Walker]

[Tim] Below

On Tue, Jun 10, 2014 at 3:31 PM, Aslak Hellesøy <aslak.h...@gmail.com> wrote:

On Tuesday, 10 June 2014 at 21:29, John Smith wrote:

Hi ,

Im trying to automate test case creation

Do you want test cases to be *created* automatically? Based on what?

Cucumber automates the *execution* of test cases (scenarios), but they still have to be created manually, by human beings. Just like code.

Aslak

[Tim] I wrote a utility called "Cuke2Rally" which would parse my cukes (it supported @tags). What it did was converted the Given/When/Then syntax to the Test Case constructs in Rally which are roughly "Test Preconditions", "Test Steps" and "Test Results". In this manner we could schedule manual testing of our cukes in to a given iteration for manual regression testing. That was very cool and worked well but the surprise utility was when we randomly/periodically scheduled manual testing for live/automated tests...why? To ensure they still passed/failed when they were supposed to and hadn't suffered any entropy over time. Just my .02, Tim

[John Smith]

Hi Aslak,

I might have to clarify "but they still have to be created manually". - this is also a process

test cases have to be created manually , but you have to create:

Process : is to open database or file, 

 - create test suite

- create test case

- create test step.

Lest say if you testing Rest API Request for example you testcases(even the most of the testing steps) are pretty much the same, you have to change them based on METHOD(GET, POST) or type(JSON, XML) but the rest steps are remaining the same, like : start the service, create Request, purse the Request, Receive respond, verify correct respond, (and then you have bunch of possible responses as part of negative testing) and so on...

You can type all  test steps manually or copy/paste in Excell shit but I'm looking for some tool to optimize this so after I can get the file and export it into HPQC.

Not sure if I explained it clear...

Thank you,

John

[aslak hellesoy]

Thanks for clarifying John.

I have never used HPQC, which might explain why it's hard for me to understand your question.

It is still unclear to me how your question relates to Cucumber. I'll make another guess:

Do you want to automate the creation of HPQC test cases (which to my understanding are manual test scripts) from Cucumber scenarios (which are automated)?

And if that is what you're after - what would be the purpose of turning automated tests into manual ones?

Aslak

[Leslie Brooks]

John, we are using HPQC with Cucumber, but not in quite the way you are describing. Here is what we do:
 - Write a requirement in HPQC. Our requirements are Cucumber scenarios (Given, When, Then).
 - Tell HPQC to create a test case from that requirement. QC creates a test case with no steps and puts the Given, When, Then into the 'Description' field.
 - Collect test cases into a Test Set.
 - Use an external tool which we wrote to select a Test Set and export it as a Cucumber .feature file.
 - Tell Cucumber to run the .feature file.

You can see more details here: https://groups.google.com/forum/?hl=en#!searchin/cukes/quality$20center/cukes/YxIqFG0Wqyo/Qg_fSWFKqXwJ

I suggest that you read 'The Cucumber Book'; it will explain that there is an easier way to manage repeated steps than the approach that you are describing.