Fiserv Auckland - Intermediate Software Test Engineer: Difference between revisions
Jump to navigation
Jump to search
Fiserv Auckland - Intermediate Software Test Engineer (view source)
Revision as of 21:46, 25 July 2024
, 25 July→Custom Development and Build Pipeline
| Line 33: | Line 33: | ||
The PTF was implemented using [https://www.npmjs.com/package/newman '''Newman'''] in a [https://nodejs.org/en '''Node.js'''] project, with a custom JavaScript reporter developed to process events emitted by Newman during execution. This allowed for real-time capture of results and detailed logs, providing clear insights into failures and partial successes. Results were sent to the PTF dashboard, as well as to a dedicated [https://www.splunk.com/ '''Splunk'''] instance for comprehensive monitoring and analysis. The PTF dashboard and Splunk implementations are detailed in the sections below. | The PTF was implemented using [https://www.npmjs.com/package/newman '''Newman'''] in a [https://nodejs.org/en '''Node.js'''] project, with a custom JavaScript reporter developed to process events emitted by Newman during execution. This allowed for real-time capture of results and detailed logs, providing clear insights into failures and partial successes. Results were sent to the PTF dashboard, as well as to a dedicated [https://www.splunk.com/ '''Splunk'''] instance for comprehensive monitoring and analysis. The PTF dashboard and Splunk implementations are detailed in the sections below. | ||
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 | 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 executed the PTF for all users concurrently in parallel, every hour. 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 executions. | The automation suite could be triggered from the Web UI, and code commits to the automation suite itself also triggered executions. | ||