Fiserv Auckland - Intermediate Software Test Engineer: Difference between revisions

Jump to navigation Jump to search
m
Line 35: Line 35:
A build pipeline was created in [https://learn.microsoft.com/en-us/previous-versions/azure/devops/all/overview?view=tfs-2018 TFS - Team Foundation Server] ''(now rebranded to Azure DevOps)'', with two VM's each running 10+ build agents. The pipeline was configured to execute the PTF concurrently in parallel, every hour, for all users. Environment variables were used to provide the PTF with FI settings and user credentials.  
A build pipeline was created in [https://learn.microsoft.com/en-us/previous-versions/azure/devops/all/overview?view=tfs-2018 TFS - Team Foundation Server] ''(now rebranded to Azure DevOps)'', with two VM's each running 10+ build agents. The pipeline was configured to execute the PTF concurrently in parallel, every hour, for all users. Environment variables were used to provide the PTF with FI settings and user credentials.  


The automation suite could be triggered from the Web UI, and code commits to the automation suite itself also triggered an execution.  
The automation suite could be triggered from the Web UI, and code commits to the automation suite itself also triggered executions.  


The VM's were set up and configured with Splunk and kept real time test results, extensive console logging tied to individual tests, as well as full API request and response traces.
The VM's were set up and configured with Splunk and kept real time test results, extensive console logging tied to individual tests, as well as full API request and response traces.

Navigation menu