2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries from 2017 up to now


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] Fwd: Re: How to setup dependencies after each test case without breaking the flow


  • Subject: [QF-Test] Fwd: Re: How to setup dependencies after each test case without breaking the flow
  • From: "Plamen Veselinov, QFS Support" <support@?.de>
  • Date: Fri, 31 Mar 2017 11:59:38 +0200
  • Delivered-to: qftest-list@?.net

Dear Marek,

if you nest dependencies instead of chaining them, your idea should work flawlessly.
Please find attached an example Test-suite. In the main dependency I have included a forced Cleanup with the ParseLogs procedure call.
Additionally there is one more dependency reference which takes care of the SUT Setup and Cleanup.

    


The test-suite is based on the CarConfigFx Demo "\qftest-4.1.3\demo\carconfigFx_en.qft"

I am not sure how you want to parse the SUT logs, but in case you need the SUT output from QF-Test use this variable {qftest:client.output.<name>},
detailed info here: https://www.qfs.de/en/qf-test-manual/lc/manual-en-user_variables.html#table_7.1

Best Regards,
Plamen Veselinov, QFS Support


On 29.03.2017 13:38, Nedvěd, Marek wrote:

Hello,

 

I am trying to add a script to my QFTest suite, which would search SUT logs for errors after each test case. However, I am having trouble to setup the dependency chain so it fires after each test case and doesn’t break the flow.

 

So far I’ve tried to add second dependency reference to the “main” dependency (Dep1 in the picture), which starts the application, but the problem is, that it breaks the flow and each time another dependency is set (DepenB), it gets after each test case reset (Cleanup of DepenB gets fired after each test case). Interestingly – the Cleanup of the main dependency (DepenA) isn’t fired.

 

More successful I’ve been by putting the parsing procedure to the Setup of the “main” dependency, then the other dependencies are saved, but the downside is, that the errors in logs would be assigned to the following test and I would have to add one  “fake” test  after the last test case. And it doesn’t feel right.

 

I hope I am somewhat clear on what I’m trying to achieve. Is there a trick how could I do that or do I have to call the Procedure in each nested cleanup?

 

 

Mit freundlichen Grüßen

Marek Nedvěd

qualitype GmbH - IT works.

_________________________

 

Marek Nedvěd

Softwaretester

 

Tel +49 351 8838 2800 | m.nedved@?.de

 

qualitype GmbH | Moritzburger Weg 67 | 01109 Dresden | Germany

Tel +49 351 8838 2800 | Fax +49 351 8838 2809 | www.qualitype.de

 

Sitz der Gesellschaft / Head office: Dresden | Amtsgericht Dresden HRB 31753

Geschäftsführer / Management: Dr. Wilhelm Zörgiebel | Dr. Frank Götz

 



_______________________________________________
qftest-list mailing list
qftest-list@?.de
https://movement.qfs.de/mailman/listinfo/qftest-list

--
_______________________________________________________________
Plamen Veselinov

E: plamen.veselinov@?.de
T: +49 8171 38648-21
F: +49 8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer
HRB München 140833   

--
_______________________________________________________________

Get the most out of QF-Test - Support directly from the authors
* Training & consulting: www.qfs.de/en/qftest/training.html
* Phone & email support: www.qfs.de/en/qftest/support.html
_______________________________________________________________

Plamen Veselinov
Development & Support

E: support@?.de
T: +49 8171 38648-21
F: +49 8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer
HRB München 140833   

Attachment: parse_logs.qft
Description: application/qftest