Setting up scehduling/storage/executing server environments

[Chris]

After a lot of convincing and a long wait, our team has decided to push through and renew our stand-alone license and purchase 2 run-time licenses for our virtual machines. I am quite new to setting up the testing environment so I'm trying to get the ball rolling and wanted to get some advice and/or feedback on the set up I have in mind, as well as clarification for some things that I am unsure of.

We plan on having 2 virtual machines set up for each run-time license: 1 for the scheduling service/storage service/executing server (VM1) and 1 to act as another remote executing server (VM2). Below are a few questions I had so far:

- I installed the Storage services to my stand-alone version and it required me to install MongoDB. Do I have to use this or can I use Microsoft SQL Server instead?

- What is being stored in the db - test results, test lists, etc?

- What service 'talks' to the repository to get the scripts from?

- Can I extract data from the db to get access to the results so I can customize my way of seeing the data?

Thanks in advance for the help and helping me understand everything better :)

 

- Chris

[Ivaylo]

Hello Chris,

I'll go directly to your questions below:

1. Since 2015 we no longer use SQL database, so we are now using much more improved storage server which uses MongoDB database. Unfortunately there is no option to choose between the two.

2. In the database is stored everything related to the remote runs, this includes: projects, tests, test lists, results.

3. The Scheduling service is the service that is taking care of the communication and the proper execution of the remote runs. Please keep in mind that depending on the setup you may need to impersonate the Scheduling service as explained in this article.

4. Extracting data directly from the database is up to you if you know how to query MongoDB database. A popular management tool is Robomongo.
Please note that you don't have to implement your own way of querying the database but use our existing functionality for exporting the test results in HTML or XML format as shown here. Once exported in one of the two formats I guess it would be much easier for you to customize the way you see the data.

Should you have any additional questions do not hesitate to contact us.

Regards,
Ivaylo
Telerik by Progress