User Tools
Writing /app/www/public/data/meta/testing/errigal_atp_guidelines_-_idms_3.1.meta failed
testing:errigal_atp_guidelines_-_idms_3.1
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| testing:errigal_atp_guidelines_-_idms_3.1 [2018/09/04 14:49] – srenshaw | testing:errigal_atp_guidelines_-_idms_3.1 [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Errigal ATP Guidelines - IDMS 3.4 SNMP Manager/EMS ====== | ||
| + | |||
| + | * Track this Kick off Meeting under IDMS-3069 - ERR 3.4 SnmpManager Regression Tests | ||
| + | * Testing on SFQA, NVQA, IDMSQA | ||
| + | * Pay attention to the dates specified in the ATP Schedule. | ||
| + | * **HARVEST**! Make sure that you are tracking your time to the correct IDMS ticket under the correct category. There is an example of harvest entries for both customers in the ATP Schedule, as well as individual tickets specified for each sheet. | ||
| + | * If you are unsure of the results of a test, or you are unsure how to carry out the test then mark the test as a Fail. Do not wait until the end of that day to discuss failures with the Dev consult. | ||
| + | * If a test fails or you're not sure how to do it please contact the developer assigned to that application (found in the ATP Schedule) ASAP. Do not wait until the end of the day to talk to the developers or until you have a number of fails. If the developers are not available please come talk to me. (More on failures in next point) | ||
| + | * In case of failures: | ||
| + | * Previous sprint with IDMS Ticket: Check who the developer of this functionality is and let them know that you are seeing a failure. They will be able to let you know if there is an issue with the test or a genuine bug. | ||
| + | * Previous sprint with no IDMS Ticket: Let myself know. | ||
| + | * Testing with different users: Clone the admin user before starting ATP’s and use that user for the duration of testing. Name it appropriately. e.g admin_sophie. Same for NOC/Carrier users. There are sample users on all QA systems, please clone them and use your own carrier/NOC account for testing. | ||
| + | |||
Page Tools
