Interview Question - Real time experience

Interview Question - Real time experience

Postby bhavya » Tue Feb 26, 2013 1:31 pm

Provide real time scenario which was challenging - need to talk about your own contribution and how it made a difference to your project
bhavya
 
Posts: 54
Joined: Mon Feb 25, 2013 4:09 pm

Re: Interview Question - Real time experience

Postby bhavya » Thu Feb 28, 2013 4:51 pm

Here are few egs for real time challenges for QA

1. Valid defects getting rejected - This is a common challenge every tester faces. Application fails sometimes using a certian data, tester attaches screenshot and steps to reproduce defects. But when developer checks application works fine in the same build and same environment. So this is an intermittent issue. And there is possibility that the defect will get rejected. So we as tester have to get logs and attach them to the defect when we encounter the same defect in future.

2. Server Migration project - Application is migrated from Websphere to JBOSS. All the necessary impact analysis was performed. Development had made necessary changes in code and released it for testing. Test team performed functional, system testing (E2E), browser compatibility testing. Performance team found Load testing was crashing down the servers. It was known there was memory leak, RCA revealed Websphere automatically closes all DB connection without developers manually coding it. And this feature is not provided by JBOSS server. So developers has to manually close each open connections strings in the code to fix this issue. Again testing had to be repeated for functional, system testing (E2E), browser compatibility testing. Load & stress testing was also performed successfully.

3. QTP fails to recognize an object - Application is automated using QTP. There is a "Start" button, and click functionality is recorded and playback works fine on the application. Project is near to completion and running the script the application freezes on "Start" button click. But the application works fine on clicking "Start" button manually. There is no change in development code, and there is no new build, no changes have been made to environment. We had to contact Mercury support (QTP was initially owned by Mercury and was later taken over by HP) to fix this issue. We could not provide or expose the application due to confidential issue. So series of calls and mails were exchanged where solutions like - trying to record the object again, descriptive programming, but none of these solutions worked. After 2 weeks a solution - do doble click on start button scripting solved the issue.
bhavya
 
Posts: 54
Joined: Mon Feb 25, 2013 4:09 pm


Return to Types of Testing

Who is online

Users browsing this forum: No registered users and 1 guest

cron