|
|
| Line 87: |
Line 87: |
| * Followed Gitflow, using feature branches for development and integrating changes into release-train branches. | | * Followed Gitflow, using feature branches for development and integrating changes into release-train branches. |
| * Contributed to quality checking at various stages before deploying code changes to production. | | * Contributed to quality checking at various stages before deploying code changes to production. |
|
| |
| ==Tools I used at Fiserv==
| |
| :* Postman for functional API testing, and developed framework for managing settings, and to be able to orchestrate API calls from a general collection to test different user scenarios.
| |
| :* SoapUI for functional API testing
| |
| :* VersionOne for managing cases/stories, test plans/session charters, bug tracking, test progress, issue(bug) tracking
| |
| :* xmind for mind maps and visual models to help test planning, execution, and reporting
| |
| :* Confluence Wiki for storing anything that might be useful for others, eg implementation details, how-to's for testing, common testing processes
| |
| :* Git & TFS version control and build server
| |
| :* Powershell scripts, mainly for speeding up repetitive tasks, eg deployments to multi-VM test environments
| |
| :* Octopus deployment engine
| |
| :* Chrome CJS Custom Javascript extension (to assist with repetitive QA specific tasks)
| |
| :* Microsoft SQL Server Management Studio
| |
| :* Visual Studio for various code development tasks
| |
| :* Microsoft Test Manager for managing test cases and suites, and recording test progress.
| |
| :* Splunk error analysis and error graphs
| |
| :* Fiddler & Blurp Suite for network traffic capture
| |
| :* Developer tools on common browsers
| |
| :* MS Office
| |