1) What helps to make good test case?

2) What are the things to wrong usually during the testing?

3) What language is LoadRunner script. based on? C

4) What did you use for metrics?

5) What results do you get after running the load test?

6) What did you do by using QTP?

7) What are the environments you can use QTP?

8) What is the percentage of the manual and automated testing usually?

9) Whom do you discuss more about the problems/issues you get?

10) As QA analyst tell me about 2 of your collogues strengths and weakness?

What is Web Architecture?

-A tester does not necessarily have to know this unless you are a very Senior Tester testing networks and doing some kind of development. However, if you want to know more about it, please visit:  http://www.objs.com/survey/WebArch.htm

What is a ‘Show Stopper’?

A show stopper is a defect or bug that stops the user for further action (testing).  It has no work around.  In other words, it stops every thing and the user cannot go any further.  This is called show stopper in software industry language.  (This is not an interview questions, but you have to know this terminology)

Does a Tester need SQL?

Answer: Yes.  For a Tester, SQL is needed.  I had the same question in mind before I came to the actual implication-what is SQL used for?  And now, I know that when we do the backend testing (see qaquestions.com for details), we need to write SQL queries to retrieve the data from the database and compare this data to the one with reports or output.  Another scenario is, if something goes wrong in the application, for example, if there is an error, then we might have to write SQL queries to retrieve the data from the database and check what went wrong.  Let’s say, we need to check in the Error Log table what went wrong.  To check this, we open the database, go to Error Log table and find out that happened.  In the Error Log table, there are many records, so which one is your error then?  To find out which one is yours, we need to write SQL queries. Example, you logged in to the application with User ID=devin99 and password=sn992jj.  Now, to retrieve your record, you can write a query some thing like this:  select * from Error Log where userID=devin99; This query will retriev your record only so that you can see what happened.

Accordingly, you wrote a defect saying that “OK” button should be changed to “Continue” button.  Now, this defect is fixed (the developer changed the “OK” button to “Continue”). Now, you started testing, there is a possibility that you might see “OK” button again.  Why?  Because you DID NOT clean your cookies.

Why do we need to clean cookies?

A tester can clean cookies by opening Internet Explorer browser and Firefox browser (whatever you are using).  We need to clean cookies BECAUSE:

99. How do you do risk assessment? (This question was asked to Mona in her interview)

Answer:  (This is what Mona answered):  The risks by understanding the infrastructure of the application, hard drive and system capabilities etc. Also added “Risk and Mitigation Strategy” column within the test plan. The major risk for the company was system getting crashed upon receiving several hits by the users . Company did not set any metrics at the development phase as to what it can handle. I told him that i noted mitigation strategy to deal with each known risk within the test plan.

CLICK HERE FOR MORE QUESTIONS…………

What is SQL and how is it used?

The following are the some of the things that a tester has to know (but may not be asked in the interview)What is a cookie?  (You must know how to clean cookies)

A small text file of information that certain Web sites attach to a user’s hard drive while the user is browsing the Web site. A Cookie can contain information such as user ID, user preferences, archive shopping cart information, etc. Cookies can contain Personally Identifiable Information.

Once we run the job, the running job finally creates an output file which is now validated by us tester. This output file can be in text format or GUI format. Thus, this is the scenario where I had to use UNIX. (I have used Linux much, however, since UNIX and Linux are the same thing, I should have no problem in using Linux)

Some of the commands I used while testing using UNIX are;

98. Please provide information (an example) of your experience testing Linux and UNIX environments (including type of system tested, how tested, actual commands and steps used for test) Testing applications using Linux and UNIX.

96. What is your weakness?

Answer: I think my weakness is that whenever I am given some responsibilities and there is a deadline for it, I work day and night, 7 days a week. This is probably bad for my family life, but I can’t sleep unless I am done with my assignments.

(Note: You should think of your weakness where because of your weakness (like the one above), still the employer benefits. DON’T SAY anything negative thing, like “I cannot work long hours, it is hard for me pick up things, it is difficult for me to understand requirement documents etc)

 97. What is your salary requirement?

$70k (negotiable), or ($35 per hour)

94. Did you get any compliments from your previous employers?  What were those situations?

Answer:  Yes. I did.  There were many occasions where I had compliments.  For example, I was testing an application going a little bit off my test cases. After I finished executing my test cases, I always think in a way what a real user would possibly click in various parts of the application. So I was just clicking back and forth and at one specific scenario, the application simply broke and displayed an error message.  That scenario was not in the test cases. The manager really appreciated me and thanked for finding this kind of critical defect.

93. Why do you want to work for this company?

Answer: (This is a tricky question.  They want to know what really interests you and you have to be careful when you answer this question.  You must admire the line of that company.  For example, if you are being interviewed by a pharmaceutical company, then tell them that you are always interested in the medical applications and the better part of your company is that it has exciting products that I am really curious to learn.  That’s why I would feel really great if I am given the opportunity to work in your company)

95. What are your strengths?

Answer: I am a very detailed oriented person. I have the sense of urgency. I can prioritize my job according to the deadline. I am very much dedicated towards my job. I am honest. I have the skills and expertise in QA process. These are some of my strengths.

91. What did you learn from your previous companies?

Answer:  I learned a lot from the previous companies wherever I have worked.  Wherever I have worked, I found out the there is always something to learn.  Different companies have different ways of working.  The environment and technology always differ from one company to another company.  I have never found one company’s environment matching with another company.  For example, if one company is using documents called requirement documents, then the other company might be using Use Cases and some companies might be using Design Document and so on.  Therefore, in my experience, there are always new things to learn in every company and we can always contribute these thing in the next company if they help to be more productive.

89.  What is your goal?

(This question is asked to check how ambitious you are as far as your career is concerned, whether you like the job you are doing and so on.  Therefore, no matter what, you should stick to your QA job at this point and say that you love this so much and your goal is some thing similar to the one below)

Answer:  My goal is to be QA Lead (or QA Manager) in near future.

90. What are you expecting from our company?

Answer:  My expectation from you company would be I will have more challenges and new things to learn and whatever the skills I have to contribute, hopefully, I will be able to contribute if they are in any way helpful to enhance productivity of the company.

88. How do you divide the application into different sections to create scripts?

Answer:  First of all, the application is divided in different parts when a business analyst writes the requirement document (or Use Cases or Design Document), he/she writes EACH requirement document for EACH module.  Let us say, if there are 12 different modules in an application that a business analyst has written the requirements for, then a tester would write the test cases for each module, which means in 12 different sections.  This is the standard practice.  There might be scenarios where you might have to break down scripts into sub-categories.  For example, if a tester is writing a script. for Login Page, he/she might write one for positive and negative testing and another sub-set of test cases would be for error message when the wrong information is entered.  In short, the test cases are divided according to the modules.

(The following questions were asked to Padma in one of her interviews very recently)

87. What testing approaches can you tell me about?

Answer: Each of the followings represents a different testing approach:

Black box testing,White box testing,Unit testing,Incremental testing,Integration testing,Functional testing,System testing,End-to-end testing,Sanity testing,

Regression testing,Acceptance testing,Load testing,Performance testing,Usability testing,Install/uninstall testing,Recovery testing,Security testing,Compatibility testing,Exploratory testing, ad-hoc testing,User acceptance testing,Comparison testing,Alpha testing,Beta testing, and Mutation testing.

 Proposed fixes are delivered to the testing environment, based on the severity of the problem. Fixes are regression tested and flawless fixes are migrated to a new baseline. Following completion of the test, members of the test team prepare a summary report. The summary report is reviewed by the Project Manager, Software QA Manager and/or Test Team Lead.

After a particular level of testing has been certified, it is the responsibility of the Configuration Manager to coordinate the migration of the release software components to the next test level, as documented in the Configuration Management Plan. The software is only migrated to the production environment after the Project Manager’s formal acceptance.

86. How do you execute tests?

Approved Test Strategy Document.

Test tools, or automated test tools, if applicable.

Previously developed scripts, if applicable.

Test documentation problems uncovered as a result of testing.

A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code and software complexity data.

Outputs for this process:

Approved documents of test scenarios, test cases, test conditions and test data.

Reports of software design issues, given to software developers for correction.

Test procedures or scripts include the specific data that will be used for testing the process or transaction.

Test procedures or scripts may cover multiple test scenarios.

Test scripts are mapped back to the requirements and traceability matrices are used to ensure each test is within scope.

Test data is captured and base lined, prior to testing. This data serves as the foundation for unit and system testing and used to exercise system functionality in a controlled environment.

Some output data is also base-lined for future comparison. Base-lined data is used to support future application maintenance via regression testing.

A pretest meeting is held to assess the readiness of the application and the environment and data to be tested. A test readiness document is created to indicate the status of the entrance criteria of the release.

85. How do you create a test plan/design?

Answer: Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. Generally speaking…

Test cases and scenarios are designed to represent both typical and unusual situations that may occur in the application.

Test engineers define unit test requirements and unit test cases. Test engineers also execute unit test cases.

It is the test team that, with assistance of developers and clients, develops test cases and scenarios for integration and system testing.

Test scenarios are executed through the use of test procedures or scripts.

Test procedures or scripts define a series of steps necessary to perform. one or more test scenarios.