↳

Be relentless

↳

Decline to release and ask if I can have time to fix the defects

↳

No

↳

Always ask what is priority. Can this wait, i have three things on my plate. confirming what is priority, and when needed. delegate tasks. Less

↳

I followed up with the customer and asked how they discovered the defect. I then determined what part of the troubleshooting process we missed that would have revealed the defect to us. Less

↳

Automation starts when UAT becomes stable. Say for instance if on each release more than 50% test are failing you don't automate the application. During this time you can run smoke or black box tests to check if major functionalities are working properly. Once it becomes more stable for instance if 20% tests are failing you can start the automation process. Depending upon the application one can start with developing the frameworks. if it needed to be a data driven framework or a key word dirven framework. The best practice will be to incorporate Hybril Framwork which is combination of both keyword and data driven frameworks. On every release you run your regression tests to check new functionalities and anything broken from the previous releases. Once the application comes closer to complition you can develop a happy path or end to end test to check the functionalities of the application. Less

↳

Any time I find myself unders stress I take a break away from my desk and try to think in the best ways to resolve the problem. Less

↳

I take short hand notes through out the day and compile them during the children's nap. Less

↳

remove injured child, wash area with soap and water, ice pack, then write an incident report. Remind children that teeth are for eating, never for biting friends. Less