Local Agent is a software component that communicates with ACCELQ server to take up test job assignments and executes them in your local application environment. It enables the cloud-based ACCELQ server to run tests remotely in the application's local network and thereby avoiding the need to expose the test application to the internet.
Depending on your requirement, you can configure Local Agent for various attributes.
- Local Agent name can be any combination of text/numerics, along with "_" character. Please note that "space" character is not allowed in the agent name. You can go up to 32 characters long.
- Port number if left empty, will be assigned dynamically on startup based on available ports.
- Authentication information that includes ACCELQ server URL, your username on ACCELQ, and the API key. You can find this information from your profile card on ACCELQ.
- Visibility (Agent Type) of an Agent can be set to Tenant, User, or Project levels
- Tenant level visibility makes the Agent available for test execution for any user belonging to your Tenant.
- User level visibility makes this agent visible to the authenticated user while working on any Project in ACCELQ.
- With Project level visibility, you can set up the names of the Projects for which this Agent should be available. Any user logging into one of these projects will have this Agent available for test execution.
- Thread concurrency determines how many jobs are allowed concurrently on this Agent. If the job requests exceed this setting, then they are queued up. It is important to size up your local agent hardware based on the expected execution concurrency. Here is some guidance for agent sizing.
- Maximum Concurrent Jobs attribute indicates the number of independent test jobs that can be kicked off at a time.
- Parallel thread count indicates the parallel execution setting that can be used within a given job. Let's say if this setting is 2, you can choose to run a given job with 2 parallel threads.
- Proxy information that includes both HTTP and HTTPS. This is necessary in case outgoing traffic in your network requires so.
- Provider type, which indicates where the test should be executed. By default, tests are executed locally on the Agent's machine. But you can choose to connect to your Browser Stack or Sauce Labs account and execute the tests on the cloud infrastructure.
- Agent auto-update (Yes/No) TBD: This flag is to indicate if the Agent should make an attempt to keep itself up-to-date with newer versions made available by ACCELQ.
- Web driver auto-update (Yes/No): This flag enables the local agent to periodically check the web driver's version compatibility with the chrome browser version running on your machine. Web driver is automatically updated in case of incompatibility.