[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [QF-Test] How to setup dependencies after each test case without breaking the flow
- Subject: Re: [QF-Test] How to setup dependencies after each test case without breaking the flow
- From: "Plamen Veselinov, QFS" <plamen.veselinov@?.de>
- Date: Wed, 19 Apr 2017 14:18:02 +0200
- Delivered-to: qftest-list@?.net
Dear Marek,
the most non obstructive way to execute an action on every TestCase exit
is to use the interface TestRunListener or its implementation
AbstractTestRunLIstener. The API documentation can be found in the
manual Ch. 41.6 "Test-run listeners".
There is a demo testsuite, which you can find in your QF-Test
installation folder \demo\runlistener\TestRunListener.qft.
You need to make a reference to your procedure for log parsing in the
'nodeExited' method and of course when 'event.getNode().getType() ==
"TestCase"' as in the example.
Best Regards,
Plamen Veselinov, QFS Support
On 19.04.2017 11:15, Nedvěd, Marek wrote:
Dear Plamen,
Thanks for the example, it of course works, but as I wrote earlier in
case of nested test-sets the “forced cleanup” option will start
triggering all other cleanup nodes in the hierarchy.
I’ll try to illustrate the problem:
I have a test suite like this:
Top Set 1
+Dependency 1 (start SUT, close SUT)
++Sub Set 1.1
+++Dependency 1.1 (open window A, close window A)
+++Sub test 1.1.1
+++Sub test 1.1.2
++Sub Set 1.2
+++Dependency 1.2 (open window B, close window B)
+++Sub test 1.2.1
+++Sub test 1.2.2
And I would like to trigger the Log Parsing after each test case. The
problem is, that If I enable forced cleanup on the node “Dependency 1”
it will also force cleanup of Dependency 1.1 and 1.2 after each test
case, which I don’t want. Those should run only after the last test in
the same test-set.
As I see it now, I would have to probably add a dependency reference
with the parsing procedure to each nested test-set.
The log parsing itself is done by server Python script.
Mit freundlichen Grüßen
Marek Nedvěd
*qualitype GmbH - IT works.*
_________________________
* *
*Marek Nedvěd*
Softwaretester
Tel +49 351 8838 2800 | m.nedved@?.de <mailto:k.kuban@?.de>
qualitype GmbH | Moritzburger Weg 67 | 01109 Dresden | Germany
Tel +49 351 8838 2800 | Fax +49 351 8838 2809 | www.qualitype.de
<http://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
*From:*Plamen Veselinov, QFS [mailto:plamen.veselinov@?.de]
*Sent:* Friday, March 31, 2017 11:55 AM
*To:* Nedvěd, Marek
*Subject:* Re: [QF-Test] How to setup dependencies after each test case
without breaking the flow
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
<mailto:k.kuban@?.de>
qualitype GmbH | Moritzburger Weg 67 | 01109 Dresden | Germany
Tel +49 351 8838 2800 | Fax +49 351 8838 2809 | www.qualitype.de
<http://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 <mailto:qftest-list@?.de>
https://movement.qfs.de/mailman/listinfo/qftest-list
--
_______________________________________________________________
Plamen Veselinov
E: plamen.veselinov@?.de <mailto:plamen.veselinov@?.de>
T: +49 8171 38648-21
F: +49 8171 38648-16
Quality First Software GmbH | www.qfs.de <http://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
|
