manager: Radhesh Radhakrishnan
teamroom: Eng.ProductCA
date: 2020-01-14
IC name: Sergiy Kachaniuk
unit: https://jira.devfactory.com/browse/PROLOGICCID-5157
insight or problem: CIMS environment creation section of E2E PROLOGICCID-5157 as described in pre-condition can be improved so that it is easier for newer Manual QA ICs to follow along
root cause: "Recommended improvements:\n1. Creating CIMS environment as documented at https://docs.google.com/document/d/1VPzh62FRrV8v_n_-K9tkTRYDXyXmLAnF9kFjrl-PV0U/edit#. When I login using the provided URL it throws an error: Invalid id: \"{ami_id\" (expecting \"ami-...\") (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.Malformed; Request ID: c22cda9c-a0a2-4959-9ede-caa397c42e2c). Simply as \n  a) Add a sub-section after Getting Access to VDI 2 for Login to VDI (https://vdi2.devfactory.com/login.html). Enter your AD credentials\n  b) Fix Typo error on Creating New VDI instance: https://docs.google.com/document/d/1VPzh62FRrV8v_n_-K9tkTRYDXyXmLAnF9kFjrl-PV0U/edit?disco=AAAAI3hDJJw \n  c) Navigate to latest VDI image for Prologic CIMS is here”\n\n2. I got this error after about 15 mins elapsed: “Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.”. Add troubleshooting information for this issue.\n\n3. Business Goal talks about a task not the actual goal that the end user is expecting. “As a user…”. The statement is vague. Specify exactly the user persona attempting the business objective. As a Cashier… or As a Manager…\n\n4. Step 1: “... connect to CIMS instance as root using ssh credentials from pre-requisite block”. Statement is vague and fails the “how” test. You already have the establishing ssh connection documentation. Change to, “Launch putty tool. Follow instructions at https://docs.google.com/document/d/1VPzh62FRrV8v_n_-K9tkTRYDXyXmLAnF9kFjrl-PV0U/edit#heading=h.acg5vjqjaykh to connect to CIMS instance as root. See ssh Credentials under User Credentials block above”\n\n5. Step 1, expected result: “To be logged in on application server under user root”. The statement is vague and can be improved by specifying the exact success message shown on the ssh terminal\n"
actions:
- what: 'Short-term: Implement the instructions as specified in Root cause section on E2E PROLOGICCID-5157.'
  when: 2020-01-17
- what: 'Long-term: Implement the recommendations for all E2Es for Prologic as majority of the suggestions go into the default E2E template and applies to all other E2Es'
  when: 2020-03-31
impact type: Q
expected result: E2E quality significantly improved, cycle-time with QA execution reduced, no additional clarifications required for even new Manual QA members.
WSPro source: Not WSPro