1. Tell me something about yourself?
I started off my career as a QA in the year ____. Since then I have worked on several operating systems such as Windows XP,2007, Windows 8 etc.Testing applications come very handy to me. I have taken care of applications in a domain such as Healthcare, CRM, ERP etc.
Being a QA, I also have experience in the field of writing. Test Plans, Test Cases are a few examples. I have also attended several meetings with project managers and business analysts.
When different kinds of testing come into question, I have explored that field as well. Whether it is Smoke Testing, Integration Testing, Regression Testing, Blackbox or UAT Testing, I have given all of them a shot.Writing defects is something other I laid special emphasis on. I would always assess, reassess, and test them thoroughly before passing it on. If the defects were not fixed, I would make the effort to reopen them again.
=================================================================================================================
2. What do you think is a test plan? Have you written one before? What does it usually consist of?
A test plan is a sort of document which analyzes the resource, scope, approach and schedule of several testing activities. It will help you to find items that need to be tested, its features that need further testing, the risks that come with some and the solutions as well.
Yes I have written a test plan before. It consists of history, contents, introduction, scope, overview and approach. The risks and assumptions are not left out either.
=================================================================================================================
3. Define a Test Case and a Use Case? What do they consist of?
A test case is again a document which gives you a step by step detailed idea on how you can test an application. It usually comprises of results (pass or fail), remarks, steps, outputs and description.
A use case on the other is a document of another kind. It helps you understand the actions of the user and the response of the system found in a particular functionality.
=================================================================================================================
4. What is a test strategy?
A test strategy helps you understand the process of testing in every software development cycle. It has been made in such a way that all project managers and developers will be informed about some of the most important issues of testing. All objectives, methods, total time and the resources which are needed for the project are explained.
A few components you will always find in a test strategy are test level and test schedules, test groups and test priorities, test summary, requirements of the environment, responsibilities etc.
=================================================================================================================
5. Name the different kinds of software testing
A more structured answer would be
1. Functional / Non-functional
1a. Non-Functional: usability, portability, performance, load, stress, endurance, soak, reliability, install-ability, maintenance-ability, security, scalability
2. White-box / Gray-box / Black-box
3. Unit tests / Integration tests (inter-app / outer-app) / System tests / UAT
4. Alpha / beta / A-B
5. Supporting types: regression, smoke
=================================================================================================================
6. What is SQL?
SQL stands for Structured Query Language. It is an American National Standards Institute computer language which is used for analyzing and assessing the database systems.The statements of SQL are used to get hold of data and retrieve it. They only work with database programs such as MS Access, Informix, Oracle, Sybase.
However there are also different kinds of SQL languages found today. They have to be in compliance with the standards of the ANSI. The keywords should be supported in the same way.
=================================================================================================================
7. Describe Change Control:
Change Control is also popularly known as Change Request. It tells us in details about the additional functionalities which are included once the Business Requirement Document has been signed off.
=================================================================================================================
8. What is a build?
A build is basically a component or a folder that contains one of the modules of the software. This is usually prepared by the Configuration Management Team.
=================================================================================================================
9. Describe the bug life cycle
Bug life cycle basically comprises of numerous statuses of an error during its life cycle. A few examples are open, deferred, solved, reopened, fixed, solved and closed. You may also speak about this process and the way in which you monitor and determine the status with the help of several points.
=================================================================================================================
10. Tell us about the biggest bug you have ever found.
In my writing experience, I have found several defects. Some of them were small whereas some of them were huge. The biggest one I have encountered so far is in the previous project on a page where I found a button called “More Information”. Once the person using the computer pressed that button, a new window would automatically pop up. I would then close the window by using three ways. First I would click on ‘X’ located on the top right corner of the page. I would then click on Close button and finally the combination keys on the keyboard.
=================================================================================================================
11. How do you plan on dealing with your team members?
There are higher possibilities that I won’t be the only one in the team. At times dealing with the team members can get very difficult and frustrating. There will be quarrelsome dispositions and misunderstandings and some will also try to ignore the other. But my purpose is to look beyond all of this. We are a team and we should work together to reach a common goal. I will be friendly and invite them over for coffee. As a human, it is very important to share feelings and have important discussions and that is exactly what I intend to do. This is something that not only me but everyone else in a working environment should apply.
=================================================================================================================
12. Have you used automation tools before?
For Automation Tools we are considering Functional Automation Testing Tools.
In some projects, used Selenium Web-driver for building Smoke and Critical Test Cases.
Also used Jmeter for performance testing to check some performance parameters.
=================================================================================================================
13. Do you like the QA job? If yes, tell us why?
Yes I do like the QA job. The only reason behind this is because the job is process oriented. This means that here I have the opportunity to do try several things at the time. I can analyze the needed documents, test the application, write test plans and test cases, prepare reports and retest them once again if the need arises. My favorite task would be reducing defects. The more defects I find while working, the happier I will be.
=================================================================================================================
14. Consider if there is no Test lead, No Test Manager and QA Manager. If you are the senior test engineer, you are getting pressure from the client to give the build. But you see that, there r 5 high and 5 low severity bugs. So, what you will do and how you interact with the client?
As you said 5 bugs are high and 5 bugs are low severity. If there is no test lead or manager not available as a senior Testing Engineer I would concentrate on 5 high severity bugs.First I will understand them and send them to the particular development team with help of project manager. If required I will explain them the situation and about the bug severity.
Also I will interact the client behalf of my test team and I will make them understand the current status of the application.
=================================================================================================================
15. Suppose a website contains 20 pages & having similar type of error in most pages. Tester checked one page & posted the bug in a bug-tracking system including that this bug remains in most pages but developer only debugged one page (the location Tester had written). Now who is responsible to check other pages Developer or Tester ?
Yes, it is responsibility of the tester to identify the bug. While Posting bugs we have to clearly specify that this bug is repeated in other screen also.
By mistake you have posted a bug saying that error is displayed in a single page ….Then there is a thing called Defect discussion where the nature of the bug is discussed with the development team at the end of the day where the development may come to know the nature of the bug.
=================================================================================================================
16. You have completed a project and release date is next day, you got one big problem but that problem can’t be resolved in short time and the estimate is 10 days. What are your options?
We could think of any workaround which would be suitable at that point of time for the problem, and make a note in the Release notes.
In case there is no workaround, then a note should be mentioned in the release notes stating it as a known issue
=================================================================================================================
17. You have tested the application and it is released. The user asks for some changes in the project and gives one week time to complete it. Out of the one week, 6 days is taken by the developer to make the changes. So you have only one day to test it. What will you do in the case in case of manual testing?
In that case we can test the main part of the application, we can found 80% of errors in that main functionality only, for that only we can mainly concentrate on main functionality.
=================================================================================================================
18. If a bug has high severity then usually that is treated as high priority, then why do priority given by project managers and severity given by testers?
High severity bugs affects the end users .Testers tests an application with the users point of view, hence it is given as high severity. High priority is given to the bugs which affects the development. Project managers assign a high priority based on development / deployment point of view.
=================================================================================================================
19. If you have executed 100 test cases , every test case passed but apart from these test case you found some defect for which test case is not prepared,then how you will report the bug?
While reporting this bug into bug tracking tool , first you will generate the test case, write the steps to reproduce the bug. Then bug will be reported.
=================================================================================================================
20. Suppose the product/application has to deliver to client at 5.00PM, at that time you or your team member caught a high severity defect at 3PM.(Remember defect is high severity)But the client cannot wait for long time.You should deliver the product at 5.00Pm exactly. What procedure you will follow?
The bug is of high severity. So we can send the application to the client and find out the priority of the feature having bug. if its priority is low, then we can hide that feature otherwise we should:-
A) explain the situation to client and ask some more time to fix the bug.
B) If the client is not ready to give some some time then analyze the impact of defect/bug and try to find workarounds for that.
No comments:
Post a Comment