Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351427 - Remote environment variables not available for screenshot
Summary: Remote environment variables not available for screenshot
Status: CLOSED INVALID
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 1.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 07:42 EDT by Michel LAURENT CLA
Modified: 2012-02-23 02:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel LAURENT CLA 2011-07-07 07:42:18 EDT
Build Identifier: 20110615-0604

If I run a AUT on a mac and the ITE (Eclipse) on Windows, I can add via AUT Configuration ENVIRONMENT VARIABLES
TEST_UDV_FOLDER=/Users/michel/TEST_UDV_FOLDER/

After starting the AUT, I can check that the variable TEST_UDV_FOLDER is present on my Mac. 

If I take a screenshot and set the destination to ${FOLDER}screenshot, I get an error execution because ${FOLDER} is not available but if I set TEST_UDV_FOLDER=/Users/michel/TEST_UDV_FOLDER/ on the windows computer (ITE), then it works fine. 

So I suppose, it doesn't use the ENVIRONMENT VARIABLE on the remote system (AUT Agent) but on the ITE... This is a problem if you want to take a screenshot with the same test suite on Windows and on Mac because it's only possible to store the picture on the computer running the AUT.



Reproducible: Always

Steps to Reproduce:
See in details
Comment 1 Alexandra Schladebeck CLA 2011-08-31 02:22:32 EDT
The environment variables are indeed all dealt with on the client side of the application (as are all things data-related). So at the moment, this works as designed. 

It is nevertheless possible to use the same test from same the client machine to save to different paths:

1. You can place a module containing your whole test (e.g. a Test Case called "FULLTEST") into two different Test Suites, each with a "Store Value" on Application at the beginning. You can use the store value to specify the path to the folder for each Test Suite. 

2. You can also achieve the same thing using a script that sets your variables before the test.
Comment 2 Alexandra Schladebeck CLA 2012-02-23 02:47:47 EST
Based on my previous comment, I am closing this ticket.