↳

No, We should not release the application with critical defects. Make sure the management team how the impact of the critical defects in the application without fixing and quality of the product not guaranteed. Less

↳

This was my favorite question as it completely illustrated how bad these guys were at interviewing. I began to ask the manager that asked the question for more information and he snapped back at me " You have all the information you need!" Really? He might as well have asked me how much it costs to build a house. Because the answer would be the same - "I need more info and detail in order to give you my estimate". Any QA worth their salt will asks tons of questions in order to understand what it is they are working on. In the end I told the panel that if I had worked on the product or similar products I would base my estimate on prior experience. If I had no prior experience I would research historical metrics from similar projects and also discuss those historical project actual development/test hours with other QA and developers to come up with an estimate. Less

↳

HPLC, GC, UV, AA, IC

↳

I'm a synergistic person. I find ways to be more efficient and share what I learn with my coworkers. I explained that if I share what I know that made my job easier, then perhaps that coworker will remember me and share what they learn back in the future with me as well as with the entire corporate structure. This is synergy. Less

↳

Too long to write, they did a great job making sure I was not just putting popular tag words on my resume to make me look more appealing. They do a great job of finding out the truth. Less

↳

know your SQL.

↳

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

↳

I would try to create a form of a prototype of said idea and present it along with taking ownership and compassion for the new feature. 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