ATEs using shared sequence but having separate databases

[jcarmody]

I was just shown two ATEs that are using a common test sequence stored on a network server.  It is desired that they both log their results to different MS Access databases, but changing the Connection String Expression on one ATE updates the Database Options on the other. 

Is it possible to share a sequence file but log results from each ATE to different databases?

[Captain_Jack · Accepted solution]

Hi Jim,

To accomplish this, you can add the DatabaseOptions ProcessModel Callback sequence to the same sequence file as your MainSequence, and then programmatically set the Parameters.DatabaseOptions.ConnectionString based on which ATE is calling the shared sequence. This assumes that your shared sequence file is using a process model.

-Jack

[jcarmody]

Thanks, Jack.

I had read about using the DatabaseOptions ProcessModel Callback but was hoping there was a way to decouple the database options from the common sequence file.