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 of 2012


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

[QF-Test] Antwort: Antwort: Re: Problem with QF Test on Jenkins CI


  • Subject: [QF-Test] Antwort: Antwort: Re: Problem with QF Test on Jenkins CI
  • From: Henrik Horneber <Henrik.Horneber@?.de>
  • Date: Thu, 8 Nov 2012 08:40:51 +0100

Hi,

never mind, it was a problem with the Jenkins node process.

Sorry for the noise.

Best Regards / Mit freundlichen Grüßen

Henrik Horneber
Continental AG, IT R&D Tires
Software Engineering
Email: henrik.horneber@xxxxxxxx
Phone: +49-511-976 / 41 93 9
Fax:   +49-511-976 / 30 26
http://www.continental-corporation.com
_____________________________________________
Continental Reifen Deutschland GmbH, Vahrenwalder Str. 9, D-30165 Hannover
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Nikolai 
Setzer; Geschaeftsfuehrer/Managing Director: Bernd Guenther, Burkhardt 
Koeller
Sitz der Gesellschaft/Registered Office: Hannover, 
Registergericht/Registered Court: Amtsgericht Hannover HRB 204239, 
USt.-ID-Nr./VAT-ID-No. DE264920698
_____________________________________________
Proprietary and confidential. Distribution only by express authority of 
Continental AG or its subsidiaries.






Von:        Henrik Horneber <Henrik.Horneber@xxxxxxxx>
An:        "Michael Höber,QFS Support" <support@xxxxxx>
Kopie:        qftest-list@xxxxxx
Datum:        07.11.2012 11:44
Betreff:        [QF-Test] Antwort: Re:  Problem with QF Test on Jenkins CI
Gesendet von:        qftest-list-bounces@xxxxxx




Hi,

this mail alerted me to the same issue in our Jenkins setup. Thanks for raising this.


We have a dedicated Jenkins slave node for QF-Test. This usually was started as a service.


I now temporarily started the node when logged in via Remote Desktop. I still get partly black screenshots (pure Swing Application). I made sure to stay connected and not locked out during the whole run,


Is this to be expected due to me using Remote Desktop (win Server 2003) or does this point to some deeper issue? (E.g. the jenkins master, which does not run but trigger the tests, running as a service?).


Best Regards / Mit freundlichen Grüßen

Henrik Horneber
Continental AG, IT R&D Tires
Software Engineering
Email: henrik.horneber@xxxxxxxx
Phone: +49-511-976 / 41 93 9
Fax:   +49-511-976 / 30 26


http://www.continental-corporation.com
_____________________________________________
Continental Reifen Deutschland GmbH, Vahrenwalder Str. 9, D-30165 Hannover
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Nikolai
Setzer; Geschaeftsfuehrer/Managing Director: Bernd Guenther, Burkhardt
Koeller
Sitz der Gesellschaft/Registered Office: Hannover,
Registergericht/Registered Court: Amtsgericht Hannover HRB 204239,
USt.-ID-Nr./VAT-ID-No. DE264920698
_____________________________________________
Proprietary and confidential. Distribution only by express authority of
Continental AG or its subsidiaries.







Von:        
"Michael Höber,QFS Support" <support@xxxxxx>
An:        
'Паша' <pavel.finkelshtein@xxxxxxxxx>
Kopie:        
qftest-list@xxxxxx
Datum:        
10.10.2012 15:05
Betreff:        
Re: [QF-Test] Problem with QF Test on Jenkins CI
Gesendet von:        
qftest-list-bounces@xxxxxx




Hello,

 
QF-Test forces the application to repaint itself to take a screenshot of the SUT (not the whole monitor). If the application embeds another technology, e.g. Swing in SWT or an OpenGL canvas in Swing, it can happen that this embedded part is black if the session is locked or the application is running within the service session. Additionally in this case the screenshots of the whole screen are usually completely black due to reasons described below.

Anyway, you should always take care to run GUI tests in an active user session. (Partially) black screenshots are only a minor problem compared with other possible troubles.

 
Best regards,

    Michael

 
From:
qftest-list-bounces@xxxxxx [
mailto:qftest-list-bounces@xxxxxx] On Behalf Of ????
Sent:
Wednesday, October 10, 2012 12:43 PM
To:
Michael Höber, QFS Support
Cc:
qftest-list@xxxxxx
Subject:
Re: [QF-Test] Problem with QF Test on Jenkins CI

 
But I have a bit different problem - black parts are only on places, where swing rendered panels are - everything else is fine. You can see this problem on screenshot, attached earlier. Right now I've temporarily solved this problem by logging in into VM and starting slave manually (not as slave), but as I understand, this operation cant be automated, isn't it?


Финкельштейн П.М.




2012/10/10 Michael Höber, QFS Support <
support@xxxxxx>
Hello,

Whenever you get black screenshots within QF-Test's run-log, it's usually the case that the tests have been executed within the Windows service session or a locked user session.
For GUI testing it's necessary to run GUI tests on a real (virtual) display. Otherwise you can run into serious troubles for grabbing screenshots, drag & drop operations (Dnd), using hard events or even recognizing components. Java WebStart applications may even fail to startup.
The way how Windows treats its sessions is to blame for these problems. Microsoft advices at MSDN/Technet to not run any GUI based applications within the service session. You can find more information by searching for the keywords "session 0 isolation" to get some technical background, especially for Windows Vista and newer.
If you start the Jenkins slave as Windows Service, the SUT also runs within this session and thus the SUT's GUI cannot be displayed and rendered like in a real non-locked user session. First of all you should ensure that the Jenkins slave is not started as service nor started via Windows Task Scheduler within the service session. You have to start it either via Windows autostart or Task Scheduler within a real user session. You should also take care that this user session does not get locked and the user stays logged in while the tests are running. This keeps the session and its context active.
If this is not possible due to security policies you should think about running the tests at virtual machines like VMWare or VirtualBox. The rules above apply for the sessions at the virtual machine itself, but of course not for the host, thus you could lock the host to prevent unauthorized desktop access.

Best regards,
   Michael


> -----Original Message-----
> From:
qftest-list-bounces@xxxxxx [mailto:qftest-list-bounces@xxxxxx] On Behalf Of ????
> Sent: Monday, October 08, 2012 2:33 PM
> To:
qftest-list@xxxxxx
> Subject: [QF-Test] Problem with QF Test on Jenkins CI
>
> Hello again!
>
> New problem here: I'm trying to integrate qf test with Jenkins. We have swing rendered panels and everything works fine on
> developers computers, but when it's running on remote computer > we've got problems with actions on such panels and black areas on screenshots (see attachment).
>
> Any ideas about it?
>
> Финкельштейн П.М.

--
Get the most out of QF-Test - through training directly from the authors
* via webinar      
http://www.qfs.de/en/info/OnlineTraining_QF-Test.pdf
* here at QFS            
http://www.qfs.de/en/info/Training_QF-Test.pdf
------------------------------------------------------------------------
QFS Support - Michael Hoeber
Quality First Software GmbH                
http://www.qfs.de
Tulpenstr. 41                         Tel: +49 8171 38648-20
DE-82538 Geretsried                   Fax: +49 8171 38648-16
GF: Gregor Schmid, Karlheinz Kellerer     HRB München 140833

_______________________________________________
qftest-list mailing list
qftest-list@xxxxxx

http://www.qfs.de/mailman/listinfo/qftest-list
_______________________________________________
qftest-list mailing list
qftest-list@xxxxxx
http://www.qfs.de/mailman/listinfo/qftest-list