Hi,
Did anyone encounter/deal with such problem?
We are using JENKINS to generate as part of nightly CI build machines to run our automation tests.
The challenge is that the created machines are created with dynamic IP address which means we can't use a STATIC and pre-configured SUT but somehow configure it along the way or through runtime.
Is there a smart and quick solution to handle this obstacle? How do we populate the SUT on the fly and have jsystem run through command-line when in fact the SUT filename we provide is not well-configured?
Thanks,
Lior
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One solution I see is to change your sysObj to query for the ip address dynamically before connect, it can be done in the system object itself or by using a separated sysObj that will manage it for you.
another solution is to manage a "sysObj manager" in the main SUT file and you will ask it for the system object you want, he will load it for you after updating the ip address in the SUT file and load using this "getSystemObject" method:
SystemManagerImpl.getInstance().getSystemObject(<System object name>, <SUT file name>, <forceNew =true/false>);
Last edit: Hovav 2013-07-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Did anyone encounter/deal with such problem?
We are using JENKINS to generate as part of nightly CI build machines to run our automation tests.
The challenge is that the created machines are created with dynamic IP address which means we can't use a STATIC and pre-configured SUT but somehow configure it along the way or through runtime.
Is there a smart and quick solution to handle this obstacle? How do we populate the SUT on the fly and have jsystem run through command-line when in fact the SUT filename we provide is not well-configured?
Thanks,
Lior
Hi Lior,
One solution I see is to change your sysObj to query for the ip address dynamically before connect, it can be done in the system object itself or by using a separated sysObj that will manage it for you.
another solution is to manage a "sysObj manager" in the main SUT file and you will ask it for the system object you want, he will load it for you after updating the ip address in the SUT file and load using this "getSystemObject" method:
SystemManagerImpl.getInstance().getSystemObject(<System object name>, <SUT file name>, <forceNew =true/false>);
Last edit: Hovav 2013-07-02
Thanks so much Hovav!
I will review this and see if it does the trick!
Appreciate your quick response.
Lior