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 23:57, 8 May 2024
, 8 May→Development of PTF Dashboard
Line 27: | Line 27: | ||
=== Development of PTF Dashboard === | === Development of PTF Dashboard === | ||
I used Node.js with Express.js and Pug to create | I used [https://nodejs.org/en '''Node.js'''] with [https://expressjs.com/ '''Express.js'''] and [https://pugjs.org/ '''Pug'''] to create | ||
* an API for receiving events from the PTF, and | * an '''API''' for receiving events from the PTF, and | ||
* a Web UI to display a snapshot of the latest results in a tabular dashboard. | * a '''Web UI''' to display a snapshot of the latest results in a tabular dashboard. | ||
The API was designed to process data from '''concurrent PTF executions''', and the Web UI '''updated in real-time''' to give immediate feedback about the environment health from multiple user perspectives. The '''fast feedback for multiple users''' was particularly useful following a '''deployment''' of the mobile API server. | |||
In addition to '''pass''' and '''fail''', I chose to also show that sometimes scenarios | |||
* '''could not run''', eg. a user with just one account could not try to transfer money between accounts. | |||
* '''pass ⚠''' when only partially successful. eg. an attempt to fetch a list of bill payments returning no items because none had been made | |||
* '''not supported''' by the FI/OLB | |||
* '''not run'''. eg. skipped, or still waiting to be run | |||
For each result cell I used '''hover and mouse actions''' to show details. | |||
[https://dirksonline.net/CV/PTF%20Dashboard.JPG Link to a '''screenshot''' of the PTF dashboard] | |||
=== Setup Splunk Enterprise === | === Setup Splunk Enterprise === |