Welcome to surfrrs.com! The intent of this website is to record our projects, track technical evolutions, provide a perspective (i.e. a QA mindset, “surfrrs vu.e”), and share our passion and devotion for Dev Ops, Jenkins, QA, Automation, and Technologies (sprinkle in connections to life, nature, and positive energy and vibe via surf and the ocean).

How-to, Runbooks

Start with a question word. The words, who, what, when, where, why, and how are concrete

Run-books

What is the User Reporting?

Why is the User seeing this issue?

How to correct the issue:

Reach out to the SME for additional help.

(Answer this Question before creating the runbook: Were you able to reproduce the issue?)

Evaluating a Tool:

1. What is the Description of Problem we are looking to resolve
2. What are the requirements:
   1. Must Haves
   2. May Haves (nice to Haves)
3. Search community for Tool
4. Set up POCs
5. Develop Tests
6. Execute Tests
7. Evaluate and Compare
8. Select tool candidate based on Requirements, Requirements met based on testing, Usability, UX, Cost, Support, (possible an intangible factor like brand recognition)
9. Perform Demo
10. Perform UAT
11. Deploy