http://missionnorman.org/emiios/3374 Q1. Can you tell me about yourself?
This is really more of a request than a question. But these few words can put you on the spot in a way no question can. Many quickly lose control of the interview during the most critical time- the first five minutes. This is not the time to go into a lengthy history or wander off in different directions. Your response should be focused and purposeful. Communicate a pattern of interests and skills that relate to the position in question. Consider your response to this question as a commercial that sells your autobiography. Provide an answer that includes information about where you grew up, where you went to school, your initial work experience, additional education and special training, where you are now, and what you intend to do next. One of the most effective ways to prepare for this question is to develop a 60-second biographic sketch that emphasizes a pattern of interests, skills, and accomplishments. Focus your response around a common theme related to your major interests and skills. Take, for example, the following response, which emphasizes QA experience and education.
“In my QA career, I have been working on various system platforms and operating systems Windows XP, Windows Vista, Windows 7, Windows 8 and UNIX. I have tested applications developed in Java, .NET, Ruby, PHP and so on. I have tested Web-based applications as well as client server applications. As a QA person, I have written Test Plans, Test Cases, attended walkthrough meetings with the Business Analysts, Project Managers, Business Managers and QA Leads. Attended requirement review meetings and provided feedback to the Business Analysts.
I have also tested Mobile Applications on different IOS and Android platforms to make sure that the applications also works accordingly in mobile devices.
I have worked in different databases like Oracle,MySQL and SQL, wrote queries to retrieve data from the database. As far as different types of testing is concerned, I have performed Smoke Testing, Functional Testing, Backend Testing, BlackBox Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing) Testing. I have participated in Load Testing and Stress Testing. I have written defects as they are found using Application Life Cycle Management(ALM)/QC, BugZero and JIRA. Once the defects were fixed, retested them and if they passed, closed them. If the defects were not fixed, then updated the status accordingly. I have also attended the defect assessment meetings as necessary. In the meantime, a continuous interaction with developers was necessary. This is pretty much what I have been doing as a QA person.
I am prepared to answer any questions you may have about my education and experience.”
This response sets a nice tone for starting the interview. The interviewee is able to say a lot within 60 seconds by staying focused. The message is clear: the interviewee has both passion and focus relating to the position. He stays on message and concludes by leaving the door open for additional questions about his education and experience. Unfortunately some candidates get off on the wrong foot by rambling on for several minutes about their childhood, family, hobbies, travels, and interests.
follow url Q2. What did you do in your last project?
Ans: In my last project, the application was a web-based application developed in Java platform. As a QA Person, I wrote Test Plans from the requirement documents and Use Cases. I performed Smoke Testing, Functional Testing, Backend Testing, BlackBox Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing). I have participated in Load Testing and Stress Testing. I attended several walkthrough meetings for requirement reviews and provided feedback to the Business Analysts. Mostly, I was in the backend testing, which required writing SQL queries directly to the database. Besides these, I wrote defects using ClearQuest. Once the defects were fixed, retested them and if the passed, closed them. If the defects were not fixed, then reopened them.
flirt foren kostenlos Q3. Have you written Test Plan? What is a Test Plan? What does it include?
Ans: A Test Plan is a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks and who will do each task (roles and responsibilities) and any risks and its solutions. What does it include? A Test Plan includes Heading, Revision History, Table of Contents, Introduction, Scope, Approach, Overview, different types of testing that will be carried out, what software and hardware will be required, issues, risks, assumptions and sign off section. A sample test plan is given below:
http://www.chezlucas.fr/?rtywwew=rencontre-avec-des-hommes-suisse&94d=dd Q4. Have you written a Test Case? What is a Test Case? What does it include?
Ans: Yes. Writing test cases is one of my main duty in my current and previous jobs. A Test Case is a document that describes step by step process of how to test the application. A Test Case mainly includes Test Case ID, Steps Description, Expected Output, Actual Output, Pass/Fail, Remarks. But it mainly depends on a organization needs and how they want their test cases to be designed. The link of some sample test case documents are given below:
هل تريد ربح المال بسرعة Q5. How many Test Cases did you write in your last project?
Ans: I wrote about 1100 Test Cases in my last project. (The reasonable number of Test Cases varies from 500 to thousands. The number 1100 test cases can be completed in a 6 month project duration).
watch Q6. What document did you refer to write the Test Cases?
Ans: Requirement document. (NOTE: It can also be Use Cases, or Design Document) (Note: It depends company to company. In some companies, they use Use Cases. In some companies, they use Requirement Documents and in some companies, they use Design Document. However, in practical scenario, most of the companies have requirement document at least).
http://dijitalkss.com/wp-json/oembed/1.0/embed?url=http://dijitalkss.com/surdurulebilirlik-aslinda-nedir/ - Impara le strategie di trading per opzioni binarie che ti faranno diventare un vero professionista. Q7. What is positive testing? Negative testing? Compare the two.
Ans: When you test an application with the correct data, ensuring that everything works as it should with expected user behavior, you are performing a positive test. For example, if a password only allows numbers, you would only put numbers into this field with a positive test. If everything works as it should, your program has passed this particular positive test.
When you test an application with incorrect data, ensuring that errors don’t occur with unexpected user behavior, you are performing a negative test. Using the previous example, you would put both numbers and letters into the password field with a negative test. If an error message occurs, you know that your program has passed this particular negative test; it didn’t let you into the system when there was unexpected behavior.
Negative testing ensures that everything works when there is unexpected user behavior, while positive testing ensures that everything works when the end user does what the program expects. In other words, negative testing makes sure that things that shouldn’t work, don’t, while positive testing makes sure that things that should work, do.
bitwis com Q8. What is a primary key? What is a unique key? How are they different?
Ans: A primary key is a column in a database where each row has a unique value. Each table has only one primary key. No NULL values are allowed. A unique key is a column or group of columns that together hold unique values. A table can have more than one unique key. For example, in a list of American Citizens, the column with social security numbers would be a primary key whereas the first and last name columns combined with phone number would be a unique key.
http://www.shyamtelecom.com/?siterko=applicazione-training-binario&fad=c1 Q9. What is the difference between requirements and specifications?
Ans: Requirements are the features, functions, and goals of the proposed software system as defined by the client. For example, a company may want their software to “Store shopping cart data for at least 30 days.” This would be a requirement.
Specifications, on the other hand, explain how these features, functions, and goals are to be met. For example, a specification would be “A user’s session information will be persisted into the operational datastore upon logout or session timeout and maintained for 30 days.”
http://inter-actions.fr/bilobrusuy/456 Q10. When do we perform functional testing?
Ans: Functional testing tests the code from end-to-end, making sure that all parts of the application are working –- even the parts that occur during failures. Functional testing should start early. Planning can be initiated during the analysis phase, and functional testing should start well before development is complete. It is common to start running functional tests within the QA department once a Minimum Viable Product is released.
see Q11. Did you have a situation where you did not have any documents (no requirement document, no Use Cases, or no Design Document) and you had to write the Test Cases? How did you write the Test Cases?
Ans: Yes. I have been to that kind of scenarios several times. There were companies where they had no documents at all. In that case, I had to discuss the application scenario and functionality with the Business Analysts or developer. I kind of prepared a document in consultation with Business Analysts and Developers and then started writing Test Cases.
see Q12. Have you worked with the Uses Cases before?
Ans: Yes. I have written Test Cases using Use Cases.
Q13. Can you tell me what a Use Case is?
Ans: A use case is a document that describes the user action and system response for a particular functionality. For example, a Use Case for ATM System can have the following user interactions:
Flows of events for the above Use Case:
System Start up Use Case
The system is started up when the operator turns the operator switch to the “on” position. The operator will be asked to enter the amount of money currently in the cash dispenser, and a connection to the bank will be established. Then the servicing of customers can begin.
System Shutdown Use Case
The system is shut down when the operator makes sure that no customer is using the machine, and then turns the operator switch to the “off” position. The connection to the bank will be shut down. Then the operator is free to remove deposited envelopes, replenish cash and paper, etc.
Session Use Case
A session is started when a customer inserts an ATM card into the card reader slot of the machine. The customer may abort the session by pressing the Cancel key when entering a PIN or choosing a transaction type.
(The above are some sample Use case flow just for understanding)
Ans: A Use Case is a document that describes the user action and system response for a particular functionality. It includes cover page, Revision History, Table of Contents, Flow of Events (normal flow and alternative flow)
Q15. What is Software Development Life Cycle?
Ans: The systems (or software) development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
It includes the following different stages:
1. Requirement phase
2. Design phase
3. Coding (programming)
5. Release (Production)
6. Maintenance (Support)
Ans: It is a document that describes the details of the application functionality which is required by the user. This document is written by the Business Analysts.
Ans: The testing of software has its own life cycle. It starts with study and analyzing the requirements.
Here is the software testing life cycle:
1. Requirement Study
2. Test Planning
3. Writing Test Cases
4. Review the Test Cases
5. Executing the Test Cases
6. Bug logging and tracking
7. Close or Reopen bugs
Ans: It is the document which describes the application functionality of the user in detail. This document is the further details of the Business Requirement Document. This is a very crucial step in the SDLC. Sometimes the Business Requirement Document and Business Design Document can be lumped together to make only one Business Requirement Document.
Ans: Coding is the process of translating the Business Design Document into the machine readable form. If the design is done in detailed manner, the Code Generation can be done without much application. Programming tools like Compilers, Interpreters and Debuggers are used to generate the code thru different high level language like C, C++, Pascal, Java.
Ans: A ‘Module’ is a software component that has a specific task. It can be a ‘link’ which can go inside to its component detail.
Ans: Before start working in a module and/or after accomplishing the testing of a module, the tester calls a meeting to disseminate his findings or to share his queries to other tester or leads of the company working on the same application that is called the Walk-thru meeting.
Ans: When each of the different modules of software is prepared, they are put in a single folder by the Configuration Management Team (CMT) and it is called the ‘Build’. In other word, the developers put their code in the shared location (folder) and all those code (modules) are combined together so that it is a complete application that works.
Ans: When the Build so prepared by the CMT is sent to different Test Environments, it is called the Build Deployment.
Ans: A test strategy is an outline that describes the testing portion of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment. The test strategy describes how the product risks of the stakeholders are mitigated at the test-level, which types of test are to be performed, and which entry and exit criteria apply. The test strategy is created based on development design documents.. It is written by the Test Manager or Lead.
Ans: No. They are different documents. Test Plan is a document that collects and organizes test cases by functional areas and/or types of testing in a form that can be presented to the other teams and/or customer where as the Test Strategy is the documented approach to testing. Test Plan is prepared by the tester whereas the Test Strategy is prepared by the QA Manager or QA lead. Both are important pieces of Quality Assurance processes since they help communicate the test approach scope and ensure test coverage while improving the efficiency of the testing effort.
Ans: It includes introduction, scope, resource and schedule for test activities, acceptance criteria, test environment, test tools, test priorities, test planning, executing a test pass and types of test to be performed.
Different types of testing carried out are:
Smoke testing (Ad-hoc testing)
User acceptance testing
Black box testing
White box testing
Note: Except the Shakeout testing and Unit testing which are respectively done by the CMT and Coder/Developer, all other testing are done by the QA Engineer (Tester).
A brief Definition of each of the above types of testing is given below:
Unit testing: It is a test to check the code whether it is properly working or not as per the requirement. It is done by the developers (Not testers).
Shakeout testing: This test is basically carried out to check the networking facility, database connectivity and the integration of modules. (It is done by the Configuration Team)
Smoke testing: It is an initial set of test to check whether the major functionality are working or not and also to check the major breakdowns in the application. It is the preliminary test carried out by the SQA tester.
Functional testing: It is a test to check whether each and every functionality of that application is working as per the requirement. It is major test where 80% of the tests are done. In this test, the Test Cases are ‘executed’.
Integration testing: It is a test to check whether all the modules are combined together or not and working successfully as specified in the requirement document.
Regression testing: When a functionality is added to an application, we need to make sure that the newly added functionality does not break the application. In order to make it sure, we perform a repeated testing which is called Regression Testing. We also do regression testing after the developers fix the bugs.
System testing: Testing which is based on overall requirements specification and it covers all combined parts of a system. It is also a black box type of testing.
Load testing: It is a test to check the user’s response time of number of users using any one scenario (single business process) of the same application at the same time.
Stress testing: In this type of testing the application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.
Performance testing: It is a test to check the user’s response time of number of users using multiple scenarios (multiple business process) of the same application at the same time.
User acceptance testing: In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to.
Black box testing: It is test where a tester performs testing without looking into the code. OR A testing method where the application under test is viewed as a black box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications. Also known as behavioral testing, since only the external behavior of the program is evaluated and analyzed.
White box testing: It is a test where a tester looks into the code and performs the testing.
Alpha testing: In this type of testing, the users are invited at the development center where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behavior of the system is noted and rectified by the developers.
Beta testing: In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers.
Ans: Testing the system or application using negative data is called negative testing, for example, testing password entering 6 characters where it should be 8 characters should display a message. When we test an application by putting negative values (instead of actual values), then the system should not allow the other values rather than the actual value. The system should give an message that the value is not correct. This is called negative testing. Another example is, if a user tries to type a letter in a numeric field, the correct behavior in this case would be to display the “Incorrect data type, please enter a number” message. The purpose of negative testing is to detect such situations and prevent applications from crashing. Also, negative testing helps you improve the quality of your application and find its weak points. (source: Jerry Ruban)
Ans: Basically Load, Stress and Performance Testing are the same. However, Load testing is the test to check the users’ response time of number of users of any one scenario of the application whereas Performance Testing is the test to check the user response time for multiple scenario of the same application.
Ans: The QA testing process that was followed in my last company where I worked was like this: First of all the Business Requirement Document was prepared as per the client’s requirement (with the muck-up screen shots). Then on the basis of the requirement document, Test Strategy, Test Plans and Test Cases were written in sequential order. Once the Build is made and deployed to the different testing environments where different types of testing were performed to check whether there are any defects.
Ans: SQL stands for Structured Query Language. SQL is an ANSI (American National Standards Institute) standard computer language for accessing and manipulating database systems. SQL statements are used to retrieve and update data in a database. SQL works with database programs like MS Access, DB2, Informix, MS SQL Server, Oracle, Sybase, etc. Unfortunately, there are many different versions of the SQL language, but to be in compliance with the ANSI standard, they must support the same major keywords in a similar manner (such as SELECT, UPDATE, DELETE, INSERT, WHERE, and others). Note: Most of the SQL database programs also have their own proprietary extensions in addition to the SQL standard.
Ans: We write SQL queries using some these tools: Microsoft SQL Server Management Studio, Oracle SQL Developer, Toad, Squirrel and Rapid SQL.
Ans: Yes. You need to. No matter whether it is a small company or big, they have a database and you need to validate the data by writing SQL queries going into the database. The stronger you are in SQL, the better the chance of getting a job.
Ans: They are:
SQL>select *from tab; -to directory of database tables
SQL>ed -to edit the queries in the notepad
SQL>/ -to run or execute the query command
SQL>create table ‘table name’ -to create a table
SQL>desc ‘table name’ -to display table with column name with type
SQL>alter table ‘table name’ -to add a columnadd ‘column name’ ‘type’
SQL>alter table ‘table name’ -to modify the name and type of a columnmodify ‘column name’ ‘type’
Ans: In a database table, the Primary Key is a column which has a unique value for each of the row within that column. It can’t have NULL value.
Ans: In a database table, the Unique Key is a column which may or may not have null value of each of the row within that column.
Ans: Data is number, character or image which has some information.
Ans: It is collection of logically related data designed in a tabular form to meet the information needs of one or more users.
Ans: It is a document that describes the additional functionality that are added after the Business Requirement Document is signed off. It can be updated in the old business requirement document or it can be a separate document. (For example, in the Business Requirement Document, on the login page, there are User Name and Password fields. The owner of the software wants to add, “If you do not have User Name and Password, please click here.” This is a change. But this change came after the document is signed off by the Project Managers. Now this is a change control and comes as a separate document. (It is also called Change Request, Modification Request).
Ans: Yes. There was a situation where in one page of an application in my previous project, when the user clicked “Contact” link, it would pop up a different window (new separate window). But it was NOT the way it was described in the requirement document. In the requirement document, when the user clicks “Contact” link, then it should navigate to another page (Not a separate new window. Then was it a problem? Functionality wise, it was NOT a problem, however, on all the other pages, when the user clicked “Contact” link, the system would navigate to next page (not a separate window). So, it was NOT CONSISTENT with the other functionality on the other pages. Therefore, it was a consistency issue. I reported this as a bug. But the Project Manager asked me to write it as a Change Control (because it requires more budget to fix this issue) so that he can address this issue at a later time. So I wrote this as a Change Control. (However, it is NOT a job of a tester to write change control. It’s the business analyst’s job)
Ans: It is a test to check whether the data displayed in the GUI front end report format matches with the particular data in the original database.
Ans: Yes I did. I was working on Reports. When I was working in my last project, this was my scenario: It was the case of testing one part of application used in the bank, where a customer comes to a bank’s front desk associate and ask for opening an account. The associate then asks for the personal information about the customer which, are the primary data, such as: First Name, Last Name, Date of Birth, Address and Social Security Number. The associate then put these primary data of that particular customer into the computer, which then afterwards batch-processed into the DATABASE in XML Format. Then the batch-processed data is sent to ETL (Extract-Transform-Load, which is software made by ‘AbInitio’ or ‘Informatica’) which processes the job to create a file to produce the report. The file is displayed to a GUI Front End report format with the help of Crystal Report/Business Object. In the GUI Front End report, let us say, if for January, the income of that person was displayed as $ 900.00, then my job was to validate this data by writing SQL queries whether this displayed data matches with the original input data in the database, being called as the Back End Testing.
Ans: I write SQL query based on the requirement document. In the requirement document, various conditions are given for the query. Based on those conditions, I write SQL query. Therefore, anything different from the requirement document is definitely a defect.
Ans: -XML stands for EXtensible Markup Language. -XML is a markup language much like HTML. -XML was designed to describe data. -XML tags are not predefined and we must define our own tags. -XML uses a Document Type Definition (DTD) or an XML Schema to describe data. -XML with a DTD or XML Schema is designed to be self-descriptive. -XML is a W3C Recommendation.
Ans: As a consultant, I am hired for a certain period of time, normally for 6 months to 1 year. Once the project is over, I needed to move to another project. That’s why you see me in the resume jumping frequently here and there.
Ans: (Note: The person who is asking this question probably wants to know how the real scenario of a working person at work. It is a hard question for those who has never worked in a work place as a Software Tester.) On the first day, normally, we will be given a computer and support people will set up the User Name and Password for the computer. If that is done already, then the QA Lead or QA Manager will give me a brief walk through of the documents (which documents are where), introduce to different team members (normally to the ones you will be working with). Then your boss will ask you to step into work what needs to be done. However, the first thing normally is, they will ask you to read the documents available for that project.
Ans: At the beginning, we all panic, what kind of questions to ask? What if they ask questions that I don’t know? Is it OK to ask questions? What do I do if I don’t know how to do the job I am assigned to? and so on. As mentioned earlier, on the first day, your Manager will give you the system (computer) (They normally call system, not computer), will tell you what the User ID and Password is, where are the QA documents on the shared drive (or Network drive) are and so on. They will definitely ask you to read a lot of documents at the beginning (And you must read read and read those documents AS MUCH AS POSSIBLE. At the beginning, allocate about 2 hours extra at home for reading these documents. This habit will put you on the top of your job). These documents are normally design specification document (DSD). Different companies call it with different names, for example, Requirement Specification Document (RSD) and so on. After reading the documents, you will be asked to write Test Plans or Test Cases (Don’t panic. The Test Plans and Test Cases templates will be give by your manager or test lead and they will tell you what to do and how to do because different companies have different formats they follow. If they don’t have one, then you can always prepare a sample from this website (see on the right column) and give it to them. You will be hero)
Ans: Now let’s say you did not understand something while reading documents. Who are you going to ask? Answer-Business Analysts who wrote this document. If you have any other questions that you don’t know, you will be asking that to you friend first, if he/she is not able to answer, then ask this question to the Lead (or Manager). Do not ask too many questions (some people get irritated). Therefore, it is important to read read and read. That’s the only way to succeed. If you have any questions in TestDirector, or QTP or any other automation tools, then there is a HELP menu as well as tutorial. Please go through these, read them before you ask any questions to anyone else. What kind of questions should I ask in the meeting? Nothing. My advice is, keep your mouth shut. Just listen. This is the best way to handle the job until you are confident enough to speak and you know what you are talking about. If they ask you some questions, then reply gently, wisely.
Ans: Most probably, you will not be the only tester in the team. There will be more than you. Sometimes, dealing with you team members is frustrating, specially when you are new. They try to ignore you. They want to show themselves smart. Don’t worry. Don’t blame them. This part of the human nature. Try to cope with it. Invite them when you go for coffee (in the coffee room in your office, don’t go outside), try to share your feelings and so on. It is all how you handle your friends. It is part of your daily activities, handle it gently. This is part of the situation I have gone through, my friends have gone through. I am just sharing this with you.
Ans: (Normally, when some one asks this question, we tend to think about automation functional testing tools, like WinRunner, LoadRunner, QTP (Quick Test Pro), Rational Robot, Experian and so on. But the reality is, even a Manual Tester also uses automation tools like bug tracking tools like TestDirector, JIRA, PVC Tracker and so on. Therefore, your answer should be Yes)
Yes. I have used JIRA And TestDirector as defect tracking tools. (Your answer is based on whether you have used automation tools specially for functional and load testing. If you have NOT used, but read about these tools, then you may be better off saying, “I know about the tools. I was involved in some of the testing using these tools, but would need some brush up in order to work independently.” I am saying this because these tools are difficult to tackle in the interview and have to know in depth. In order to pass the interview on functional automation tools, it may not be easy unless you really know the stuff. But, since there is not much to learn in JIRA and TestDirector, you only have to know what different types of fields are there in the defect logging window when writing a defect.)
Ans: When we log a defect, we see Defect ID (it shows later in TestDirector), Summary (where we write short description of the defect), Description (long description of the defect), Detected by (Person who found the defect, (it’s you), Severity (meaning-is the defect critical? High? Medium? Or Low?), Date, Detected in Version, Priority, Project, Status, Assigned to and so on. Click the link below to see the fields when you report defects in JIRA or TestDirector:
Ans: I am a team player. I get along with team members very well. As far as the working is concerned, I can be equally productive in team or working alone. (Caution: Never say, I like working alone. This could lead you to not getting a job as they are always looking for people who can get along with other people.)
Ans: No. I never had that type of situation wherever I have worked. (Even if you had one, it’s a good idea to say “No”. This could be a red flag, which might stop you from getting the job)
Ans: The best thing I like about a Manager is that the Manager should be able to coordinate with the other teams so that we can get the updated documents, for example, updated requirements documents right away. A Manager who can efficiently in distributes the work to the team, without being biased and easily accessible and protective to his team for the right cause. As far as “what I don’t like” is concerned, I don’t like a manager who keeps coming to desk 10 times a day to check my work even if it is just a regular work. Once the responsibility is given, the team member should be trusted and let his work done.
Ans: I see myself a QA Lead in another 5 years. (You can also say “QA Manager”, but since the QA Manager is taking your interview most of the time, they some times feel challenged. Therefore, it might be a good idea to limit you to QA Lead)
Ans: I am in QA because I like this job.
Ans: I like this job, because it is process oriented. Meaning that I get an opportunity to work from analyzing the requirement documents to writing test plans, test cases, testing the application, logging defects, retesting, preparing reports and finally testing in production as well. Therefore, I am involved from the very beginning to the end of the software development life cycle (SDLC) process. I like this. Another reason is I like to find defects. I enjoy logging defects. The more defects I find, the happier I am.
Ans: First of all we have the test cases (or test scripts) that are written based on the requirement document. This pretty much covers what functionalities to test. Therefore, looking at the test cases tells us what to test in the application.
Ans: Well, this is a situation where I have come across several times. Some of the companies in my previous projects did not have any documents. In this case, I went to the Business Analyst and some times to developers to find out how exactly the functionalities work, how to navigate from one page to another page and so on. After getting a clear vision, I write test cases based on the conversation (which is a step by step procedure to test an application) and get ready for testing.
Ans: Once you find a defect, this is what we need to do: 1. Recreate the Defect: Once you find a defect, we must try to recreate (meaning that we should be able to reproduce it) at least 3 times so that we are sure that it is a defect. Some times, once we find it log it without recreating, may put us in a false situation (because sometimes the application does not behave in the same way). Therefore, it is important to recreate the same defect several times. 2. Attach the Screen Shot (supporting document): Once we confirm that it is a defect, and then it is a good idea to attach supporting documents when we log (write) a defect. For example, screen shot, requirement document etc. For instance, let us say that instead of “Continue” button on a page, there is a typo “Continue”. Now, we will make a screen shot of this page (To make screen shot, press “Print Screen” button on the keyboard, and open a Word document, and Click Edit on the Word document and “Past” it. You will see the screen now) Now, a tester needs to write defects in easy and clear language to make all the developers to understand easily. 3. Log the Defect: Now, the next step is, we need to log it. Depending on the company what kind of tools they are using (for example, some companies use TestDirector to log defects, some companies use Rational ClearQuest, some use PVC Tracker and so on). If the company is small and cannot afford these expensive tools, then they may simply use Excel sheet to log defects. We log the defect.
Ans: Basic elements we put in a defect are: SEVERITY, PRIORITY, CREATED BY, VERSION NO, HEADER, DESCRIPTION OF THE DEFECT where we write how to recreate a defect, in what module the defect is found, Status, and so on.
Ans: Well, there are many big defects I have found in various projects. For example, in the last project, on a page, there was a button called “More Information”. Once the user clicked that button, the system would open a new window (pop up). We could close the new window in 3 ways: -By clicking X at the top right corner of the page -By clicking “Close” button on the page -By pressing combination keys (Alt+F4) on the key board Although the combination key (Alt+F4) was not mentioned in the test case, I just wanted to try how the application reacts when Alt+F4 is pressed. Then I pressed Alt+F4. The result was a disaster-the application crashed (broke). The application disappeared from the computer monitor. Since it was the last day of testing for us, it brought chaos in our Managers, Leads and the whole teams. Finally, the developers disabled Alt+F4 as a temporary solution and the application went into production.
Ans: There is a certain process how the quality of software is guaranteed (ensured). If is defined by the ‘exit criteria’. (What it means is, a QA Manager writes a document called Test Strategy. This Test Strategy defines the ‘exit criteria’.) Exit Criteria gives the measurement, for example, in order to confirm the quality, how many critical defects, high defects, medium defect and low defect are acceptable? These are all defined in the exit criteria. (Normally in practice, for a quality software, there should no critical defects (0 critical), no high defect (0 high), no medium defect (0 medium) and may be 1 low defect)
Ans: When I find the defect that normally others don’t find, then I feel very proud. For example, there were situations where I found bugs that crashed the whole system at the end of testing phase. I tried the scenarios where the scenarios were NOT mentioned in the test cases. For example, we can close the windows by clicking X on the page, with “Close” button and so on. But there is another way that you can close the window, by pressing Alt+F4 on the keyboard. Not many testers test this scenario. I have done this in my last two projects. Both the time, the application crashed which became a big issue. I felt proud.
Ans: I am a very detailed oriented person and I like process-oriented job. The way QA process works is just the kind of work I like. For example, analyzing requirement documents, attending walk-through meetings, writing test plans, writing test cases, executing the test cases (or running the test cases) testing the application, logging defects, retesting them and so on. I think I really like the process and that’s why I chose this career.
Ans: We should start testing as soon as the following things are ready: -Test Data are ready -Build (all the developers have coded their code and merged them together) -Test Environment (servers, network etc) is set up and ready -When the manager asks us to go ahead and start testing.
Ans: First of all, I will look at the requirement documents (or design document in some companies). The requirement document will tell us what the functionalities in the application (software) are. Once I analyze the requirement documents (one module=one requirement document). After that, I will write test plans for each module (one module =one test plan). Then after the test plan is complete, I will write test cases (One module can have hundreds, even thousands test cases). Once the test cases are ready and the application is ready (or once the build is ready), then I will start testing. Before I start testing, however, I will make sure the test environments, test data and defect logging tools are in place. This is how I will go about testing an application.
Ans: A bug is a bug is an error, flaw, mistake, failure, or fault in a computer code (program) that prevents it from behaving as intended (e.g., producing an incorrect result). (You can also add this: When the expected results (accordingly to the requirement documents) don’t match with the actual results (while testing), then it is considered a bug)
Ans: The testing coverage is defined by exit criteria (There is exit criteria and entry criteria in the Test Strategy). For example, if the exit criteria says “The software will be acceptable to the client only if there are no critical defects, no high defects, no medium defects and only two low defects”, then all the critical, high, medium should be zero. Only 2 low defects are acceptable. Thus, 100% coverage is measured by the exit criteria. Also, 100% test cases must be executed in order to cover 100% of testing.
Ans: (You will be OK if you just give one of the problems below, not all of them) I had many problems while testing applications in the past. As far as I remember one of them (then describe one of them from below), this was the scenario: (i) It was a web-based application. I was working on a module called “Transaction Summary”. There was “Submit” button on that page. After entering data in the all the fields, for example, First Name, Last Name, Social Security Number, Date of Birth and so on, I clicked the Submit button. Once I clicked Submit button, an error page displayed, “Page cannot be found…”. Since it was a critical defect, I immediately informed the Test Lead. There was a chaos in the room. All the developers, Database Administrators and Testers gathered in my cube (room). No body could tell exactly what was wrong with it. Finally, one smart guy checked into the database and found out that one of the files in the database was closed. The status of all the files should be in the open status. Once the status of the closed file was put in the “open” status, the application worked fine. (ii) One of the problems was in the Login window (page). When the user enters and Login Name and Password, then Password should be encrypted.
One of the Test Cases was that I needed to open database and see whether the password is encrypted or not. I found out it was not encrypted. I reported it as a bug (defect) and it was fixed in the next release (build). (iii) Defects I have found in a project was a defect to close a window (pop up). For example, in the last project, on a page, there was a button called “More Information”. Once the user clicked that button, the system would open a new window (pop up).We could close the new window in 3 ways: -By clicking X at the top right corner of the page -By clicking “Close” button on the page -By pressing combination keys (Alt+F4) on the key board Although the combination key (Alt+F4) was not mentioned in the test case, I just wanted to try how the application reacts when Alt+F4 is pressed. Then I pressed Alt+F4. The result was a disaster-the application crashed (broke). The application disappeared from the computer monitor. Since it was the last day of testing for us, it brought chaos in our Managers, Leads and the whole teams. Finally, the developers disabled Alt+F4 as a temporary solution and the application went into production. (iv) Another problem was that a user would search for branch location information of a bank. The user logs in by using User Name and Password. After the log in, on the “Search Location” page, the user enters and zip code of the location he wants to find, then clicks Find button. After that the system (application) gives a number of branch locations. The user now clicks “Request Information” for one of the branches. As soon as the user clicks “Request Information” button, the application breaks (displays “Page cannot be found” error). I logged this defect as a critical defect.
When the developers and database administrator looked into it, then they found out that in one of the tables, the data was not recorded. In all the tables (UserProfile table, ClientID table and SessionID table), the data should be populated with the information entered by the user. For some reason, in one of the tables, it was blank (null). Once they wrote a small code to populate data (enter data) to the table, the application started working. (v) In my previous project, when the customer wants to upload a document, for example, a copy of a monthly statement (in Word format), on the website, the system should automatically change the Word document into .pdf format. Once the document was uploaded, I saw that the fields in the .pdf document were interchanged (misplaced). For example, the First Name displayed in the Last Name section. Date of Birth displayed in the Social Security Number field and so on. We found out that the problem was a mapping problem (remember this word). Once the mapping was correct, I tested in the new build. It was fixed. (vi) The most common problem that I have faced in my previous projects are the Java script errors, data connectivity, error, HTTP 500 error (This error occurs when server is down), HTTP 400 error (when file is not found) and so on.
(vii) “Father” pop up displayed when Print/Print Preview button clicked. (This was coded by the developer to mark this coding portion (for his/her own purpose as a mark to indicate where he/she made changes, however, forgot to remove it). Once the developer fixed it, it still displayed the same thing (because it was in the servers memory and could not go). Now, I had to reset memory of the server from my machine. Therefore, what I did is, I went to the website I was testing (for example, http://mysite.app.org/My_profile) and added reset.aspx at the end of the URL (Now the URL becomes http://mysite.app.org/My_profile/reset.aspx and hit enter. It took me to the server memory and I selected section and submitted the query and it was cleared. Retested again and it is now OK.
(viii) I was testing a web application. On one page, I clicked Save & Continue button twice (my mistake). Once this button is clicked twice, the system displayed an error message, “Could not save the answers, please contact technical support”. (When clicked only once, the button works fine.).
Solution: Once the user clicks the button once, the button was disabled later so that the user cannot click twice. (ix) I was testing a web-based application. Once all the fields are entered on the one of the pages, we had Print Preview button. If the user clicks this button, we were supposed see the same information in a new window in PDF format. While looking at the data in PDF file, there were some fields missing, for example, Date of Birth was missing in the PDF file.
Ans: (Here, you should be careful not to say any negative words about the past boss. This will give a reflection that you cannot work with different nature of people. You should be able to show them that you can cope with any king of boss. Therefore, just take an idea below how the answer should be.) I can hardly think of any Manager that was really bad. But when I compare, then I remember of a Test Lead who was just made a lead from the developers team. She used to feel that she has been very proud of her position and used to boss around. Some times, she used to call home and check where I was and what I was doing. Or have I completed my job before leaving and so on. I think, whatever she did, was in the benefit of the company and myself in the long run which would give me more confidence in future.
Ans: The best thing I like about QA is, I like the job which is more process oriented. For example, we have to work right from reading the requirement documents, providing feedback to the Business Analysts as necessary, writing test plans, test cases, execute the test cases, interaction with different developers, attend walk-through meeting and so on. I am a very detailed oriented person. When I test applications, I try to get into the depth of functionality so that I don’t miss out anything. Finally, I love logging defects.
Ans: The basic elements in a defect report are: Defect ID, Header, Description, Defect Reported by, Date, Status, Version, Assigned to, Approved by, Module where the defect was found and so on.
Ans: Verification: Verification is a process to ensure that the software that is made, matches the original design. In other words, it checks whether the software is made according to the criteria and specification described in the requirement document. It is to check whether you built the product right as per design. It is a low level checking. (It is done in walk-through meetings generally). It checked whether it is made accordingly to the design.
Validation: Validation is a process to check whether the product design fits the client’s need. It checks whether you built the right thing. It checks whether it is designed properly.
Verification Vs. Validation
Verification is testing that your product meets the specifications / requirements you have written. “Did I build what I said I would?”.
Validation tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. “Did I build what I need?”
V&V together make sure that your software has delivered on its purpose in an error-free (ideally) way.
Ans: Every company has entry and exit criteria. When we test applications, we refer to exit criteria. When we are about to finish testing, then the QA Team (QA Manager) refers to the exit criteria (exit criteria tells the level of defect that you can be comfortable with before it goes to production. For example, there should be ZERO critical defect, ZERO high level defect, ZERO medium defect, 1 Low level defect, all the test cases must be 100% executed etc). Once the exit criteria meet the requirements, then the software is considered to be sufficiently tested. Every company has entry and exit criteria. When we test applications, we refer to exit criteria. When we are about to finish testing, then the QA Team (QA Manager) refers to the exit criteria (exit criteria tells the level of defect that you can be comfortable with before it goes to production. For example, there should be ZERO critical defect, ZERO high level defect, ZERO medium defect, 1 Low level defect, all the test cases must be 100% executed etc). Once the exit criteria meet the requirements, then the software is considered to be sufficiently tested.
Ans: Test scenarios are derived from requirement documents. We follow each and every functionality (called business rules) mentioned in the requirement document. One functionality can have multiple business rules. For example, let us say in there is one requirement called “Login”. This “Login” may have various scenarios. For example, one scenario is, enter the right User ID and wrong password. The system should display an error message. Another scenario would be to enter wrong User ID and right Password. The system should display an error message. The third scenario could be to enter the right User Name and right Password. The system should allow the user to get into the system. This is how the test cases are derived from the requirement documents or from the Use Cases.
Ans: We write test cases for smoke testing, integration testing, functional testing, regression testing, load testing, stress testing, system testing and so on.
Ans: I have never written separate Test Cases Integration Testing. Since Integration Testing is a test to check whether the all the modules are integrated together or not (meaning that when the developers compile all their module and make a build, all modules should be working when they are combined together and those modules when combined, should work as expected). If they are not integrated (combined) in a nice way, then the application breaks. Basically, when we do the functional testing, the integration testing is automatically done. This is my experience.
Ans: Regression test cases are also based on the requirement documents. They are written more into detail and with every release (build), the testers need to do regression testing. The criteria for regression testing are; there should be no major defects while we do our smoke test and functional testing.
Ans: Yes. It depends upon the company how the company has followed the numbering of test cases. However, normally, it is just a simple numbering in most of the time (see previous questions of qaquestions.org). But some companies may also relate this numbering to the requirement number. For example, if the requirement for Login is “REQ-LOG-001”, then we can number the test cases like REQ-LOG-001-001 and so on.
Ans: (Definition from www.wikipedia.org) “In software testing, a test harness or automated test framework is a collection of software and test data configured to test a program unit by running it under varying conditions and monitor its behavior and outputs. It has two main parts: the test execution engine and the test script repository.”
Ans: The way of writing Test Plan and Test Cases is the same in all the test phases. However, specifically for User Acceptance Testing, the testers use data nearly real data (meaning that the data is very much similar to the production data or real data).
Ans: There are various reports we normally prepare in QA: · Test summary Report – It is a report that has list of the total test cases, list of executed test cases, remaining test case to be executed, executed date, pass/fail · Defect Report – In this report we normally prepare a list of defect in spreadsheet e.g. defect # CQ12345 [ if you log a defect in the application called Rational ClearQuest] · Traceability Matrix [also called RTM (Requirement Traceability Matrix)] Report – the document which shows the relationship between the functionality or the business rules and the test cases. So, with the help of Traceability Matrix we make sure that we includes all the functionality in our test cases according to the requirement document.
Ans: I would describe this as below: A Tester finds a defect and logs it. (But before you log it, you must try to recreate it for 3 or 4 times so that you are 100% sure that it is a bug) The defect is now approved or disapproved by the Test Lead. (If it is disapproved, then the test lead will come to you ask for more details and you have explain to him why it is a bug) After the Test Lead approves the bug, it is now assigned to a development Team Lead (or Development Manager). He/she now assigns that bug to the concerned developer. The developer now looks into the bug and fixes it. Once the fix is ready, there will be another build ready to test. The tester now tests the defect. It the defect is fixed, then the tester closes the defect, if not then the test will reopen it and same cycle starts.
Ans: If the developer does not accept the defect, then he will reject it. Once it is rejected, then it comes back to the tester. Now, the tester will ask for clarification with the developer why the defect is rejected. Since everything is based on the requirement documents, both tester and developer will have to look at the requirement document, validate it and then reopen it if necessary or close.
Ans: For both client server and web based applications, the testing is the same except one thing: We test web based applications in different browsers, for example, Internet Explorer (will test in different versions like IE 8.0, IE 9.0, IE 11.0), Firefox, Safari (for Mac) and so on where as for client server, we don’t need to test in the browsers.
Ans: An inspection is a formal meeting, more formalized than a walkthrough and typically consists of 3-10 people including a moderator, reader (the author of whatever is being reviewed) and a recorder (to make notes in the document). The subject of the inspection is typically a document, such as a requirements document or a test plan. The purpose of an inspection is to find problems and see what is missing, not to fix anything. The result of the meeting should be documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before the meeting starts; most problems are found during this preparation. Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug prevention is more cost effective than bug detection.
Ans: Poorly written requirements, unrealistic schedules, inadequate testing, adding new features after development is underway and poor communication. Requirements are poorly written when requirements are unclear, incomplete, too general, or not testable; therefore there will be problems. The schedule is unrealistic if too much work is crammed in too little time. Software testing is inadequate if none knows whether or not the software is any good until customers complain or the system crashes. It’s extremely common that new features are added after development is underway. Miscommunication either means the developers don’t know what is needed, or customers have unrealistic expectations and therefore problems are guaranteed
Ans: Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented. Ideally, there should be a system for easily finding and obtaining of documents and determining what document will have a particular piece of information. Use documentation change management, if possible.
Ans: In this situation the best bet is to have test engineers go through the process of reporting whatever bugs or problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules and indicates deeper problems in the software development process, such as insufficient unit testing, insufficient integration testing, poor design, improper build or release procedures, managers should be notified and provided with some documentation as evidence of the problem.
Ans: This can be difficult to determine. Many modern software applications are so complex and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are… Deadlines, e.g. release deadlines, testing deadlines; Test cases completed with certain percentage passed; Test budget has been depleted; Coverage of code, functionality, or requirements reaches a specified point; Bug rate falls below a certain level; or Beta or alpha testing period ends.
Ans: Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions: · Which functionality is most important to the project’s intended purpose? · Which functionality is most visible to the user? · Which functionality has the largest safety impact? · Which functionality has the largest financial impact on users? · Which aspects of the application are most important to the customer? · Which aspects of the application can be tested early in the development cycle? · Which parts of the code are most complex and thus most subject to errors? · Which parts of the application were developed in rush or panic mode? · Which aspects of similar/related previous projects caused problems? · Which aspects of similar/related previous projects had large maintenance expenses? · Which parts of the requirements and design are unclear or poorly thought out? · What do the developers think are the highest-risk aspects of the application? · What kinds of problems would cause the worst publicity? · What kinds of problems would cause the most customer service complaints? · What kinds of tests could easily cover multiple functionality? · Which tests will have the best high-risk-coverage to time-required ratio?
Ans: Work with management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application’s initial design allows for some adaptability, so that later changes do not require redoing the application from scratch. Additionally, try to… · Ensure the code is well commented and well documented; this makes changes easier for the developers. · Use rapid prototyping whenever possible; this will help customers feel sure of their requirements and minimize changes. · In the project’s initial schedule, allow for some extra time to commensurate with probable changes. · Move new requirements to a ‘Phase 2′ version of an application and use the original requirements for the ‘Phase 1′ version. · Negotiate to allow only easily implemented new requirements into the project; move more difficult, new requirements into future versions of the application. · Ensure customers and management understand scheduling impacts, inherent risks and costs of significant requirements changes. Then let management or the customers decide if the changes are warranted; after all, that’s their job. · Balance the effort put into setting up automated testing with the expected effort required to redo them to deal with changes. · Design some flexibility into automated test scripts; · Focus initial automated testing on application aspects that are most likely to remain unchanged; · Devote appropriate effort to risk analysis of changes, in order to minimize regression- testing needs; · Design some flexibility into test cases; this is not easily done; the best bet is to minimize the detail in the test cases, or set up only higher-level generic-type test plans; · Focus less on detailed test plans and test cases and more on ad-hoc testing with an understanding of the added risk this entails.
Ans: It may take serious effort to determine if an application has significant unexpected or hidden functionality, which it would indicate deeper problems in the software development process. If the functionality isn’t necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only affects areas, such as minor improvements in the user interface, it may not be a significant risk.
Ans: Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings and promote training as part of the QA process. However, no one, especially talented technical types, like bureaucracy and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug fixing and calming of irate customers.
Ans: Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly. Let us say, for example, the currently software is in the mainframe system which calculates the interest rate. The company wants to change this mainframe system to web-based application. While testing the new web based application, we need to verify that the web-based application calculates the same interest rate. This is parallel testing.
Ans: System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment. The purpose of system testing is to validate an application’s accuracy and completeness in performing the functions as designed. System testing simulates real life scenarios that occur in a “simulated real life” test environment and test all functions of the system that are required in real life. System testing is deemed complete when actual results and expected results are either in line or differences are explainable or acceptable, based on client input. Upon completion of integration testing, system testing is started. Before system testing, all unit and integration test results are reviewed by Software QA to ensure all problems have been resolved. For a higher level of testing it is important to understand unresolved problems that originate at unit and integration test levels. You CAN learn system testing, with little or no outside help. Get CAN get free information. Click on a link!
Ans: Similar to system testing, the *macro* end of the test scale is testing a complete application in a situation that mimics real world use, such as interacting with a database, using network communication, or interacting with other hardware, application, or system.
Ans: Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.
Ans: Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Ans: Compatibility testing is testing how well software performs in a particular hardware, software, operating system, or network environment.
Ans: Comparison testing is testing that compares software weaknesses and strengths to those of competitors’ products.
Ans: Acceptance testing is black box testing that gives the client/customer/project manager the opportunity to verify the system functionality and usability prior to the system being released to production. The acceptance test is the responsibility of the client/customer or project manager, however, it is conducted with the full support of the project team. The test team also works with the client/customer/project manager to develop the acceptance criteria.
Ans: The Test/QA Team Lead coordinates the testing activity, communicates testing status to management and manages the test team.
Ans: One software testing methodology is the use a three step process of… 1. Creating a test strategy; 2. Creating a test plan/design; and 3. Executing tests. This methodology can be used and molded to your organization’s needs. Rob Davis believes that using this methodology is important in the development and in ongoing maintenance of his customers’ applications.
Ans: The general testing process is the creation of a test strategy (which sometimes includes the creation of test cases), creation of a test plan/design (which usually includes test cases and test procedures) and the execution of tests.
Ans: The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment. Inputs for this process: · A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data. · A description of roles and responsibilities of the resources required for the test and schedule constraints. This information comes from man-hours and schedules. · Testing methodology. This is based on known standards. · Functional and technical requirements of the application. This information comes from requirements, change request, technical and functional design documents. · Requirements that the system can not provide, e.g. system limitations. Outputs for this process: · An approved and signed off test strategy document, test plan, including test cases. · Testing issues requiring resolution. Usually this requires additional negotiation at the project management level.
Ans: 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. 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. Inputs for this process: 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.
Ans: Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoint meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and discuss testing issues, status and activities.The output from the execution of test procedures is known as test results. Test results are evaluated by test engineers to determine whether the expected results have been obtained. All discrepancies/anomalies are logged and discussed with the software team lead, hardware test lead, programmers, software engineers and documented for further investigation and resolution. Every company has a different process for logging and reporting bugs/defects uncovered during testing.A pass/fail criteria is used to determine the severity of a problem, and results are recorded in a test summary report. The severity of a problem, found during system testing, is defined in accordance to the customer’s risk assessment and recorded in their selected tracking tool.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.
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.
Ans: 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) (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)
Ans: $70k (negotiable), or ($35 per hour)
Ans: I have tested applications using UNIX. For every backend testing I have done in the past, I have used UNIX platform while performing backend testing. For example, when the data is fed into the system in the front end, that data goes to the database after the batch processing. From the database, the data is now sent to the ETL system (in XML format) for data manipulation as per our need (ETL is a software tool of Ab Initio company which is used to manipulate data in the data warehouse). In the ETL system, we manipulate those data according to our need), for example, it could be income statement of the company, balance sheet, monthly reports, and so on. In order to produce income statement, we need to run a job in ETL. To run this job, we use UNIX. In the same way, different types of jobs are created for each need (creating balance sheet is another job, creating reports is next job etc) then I had to run different jobs in the ETL system. 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:
Ls –l ———>to check the file list
Pwd———→ to see which directory I am in
Cd ———–>change the directory
Cd .. ———>change the directory one level up
Mkdir ———>make a directory
Rmdir ———>Delete the directory
setenv name v ——>Set environment
kill% ——–>Kill the running job
vi ———>editor Used to write scripts more
cat —–>list contents of the file
chmod ——–>change permission
rm —–>delete a file
Q113. What is a cookie?
Ans: (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.
Ans: Yes. A tester has to know HOW TO CLEAN cookies (Does not have to know the definition)
Ans: Cookies are cleaned in the browsers like IE (Internet Explorer), Firefox, Safari (for MAC and windows both), Netscape and so on. However, the mostly used (90%) browser is IE (Internet Explorer).
Here is how you clean cookies in IE (Internet Explorer):
1. Open IE (Internet Explorer) 2. On the menu, click Tools–>Internet Options–>Click Delete button (It is in General Tab) (You will see different buttons now, for example, Delete Files, Delete Cookies, Delete History, Delete Forms, Delete Passwords, Delete All). 3. Click Delete All button. Now the cookies are cleaned in IE.
Here is how you can clean cookies in Fire Fox:
1. Open Firefox Brower. 2. Click Tools. 3. Click Error Console. 4. Click Clear. Now the cookies are cleaned in Firefox.
Ans: Yes. For a Tester, SQL is needed. I had the same question in mind becore 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 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.
Ans: 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 futher. This is called show stopper in software industry.
Ans: 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.
Ans: 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.
Ans: I want to be QA Lead in another two years.
Ans: QA is the only thing I love doing it. I love this job and want to progress in this sector. I want to know how to manage QA process, how to handle different jobs and so on. Since the next step is the QA Lead, that would preferably be one I will targeting for.
Ans: (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)
Ans: 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 possibally 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.
Ans: 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.
Ans: 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)
Ans: My goal in the next 4 years is to be a QA Manager.
Ans: Tractability matrix is used to cross check the test cases as per the requirement of the test cases. In other words, it checks whether the each functionality is covered in the Test Cases as per requirement document. (We create RTM using Quality Center/ALM tool)
Q127: Create TEST SCENARIOS for testing an elevator
Verify elevator goes up
Verify user is able to go to top floor from basement
Verify user is able to go to top floor from ground floor
Verify user is able to go to any middle floor section from ground floor
Verify user is able to go to top floor from any middle floor
Verify parked elevator on any lower floor goes up when user calls elevator from any upper floor
Verify elevator goes down
Verify user is able to go to basement from ground floor
Verify user is able to go to basement from any middle floor section
Verify user is able to go to basement from top floor
Verify user is able to go to ground floor from top floor
Verify user is able to go to ground floor from any middle floor section
Verify parked elevator on any upper floor goes down when user calls elevator from any lower floor
Verify elevator is safe
Verify elevator alarms if overloaded and is more then passenger limit
Verify elevator doors open when open door button is pressed
Verify elevator doors close when close door button is pressed
Verify elevator doors open when sensor detect user in between pathway
Verify elevator is in sync with floor display panel
Verify elevator floor indicated in floor display panel is the same with the floor where elevator is located
Q128. What are direct and indirect scenarios in Testing?
First, it depends on the way the organization defines things – what a particular business considers direct and indirect scenarios could well be different than what you’d expect.
If I was responding to this question in an interview, I’d start by saying that in my experience direct scenarios are those where the test explicitly exercises the requirement or function being tested, and indirect scenarios are those where the results have to be inferred from the tester’s observations.
I’d also give some examples, such as:
- Direct testing scenario – Date of birth has to be in the format MM/DD/YYYY. To test this, enter date values such as 1/1/11 – (should be invalid or depending on the specifications/use cases converted to 01/01/2011), 20/12/1967 (should be invalid), 12/20/1967 (should be accepted) and so forth.
- Indirect testing scenario – Address will be validated by GIS services. Here you don’t actually have access to the services and you may or may not have logging showing the call – but you can enter a real address and one that you know doesn’t exist (e.g. a street that is not in the town you enter, or a street number that doesn’t exist on that street) and infer that if the page shows a level of confidence indicator for the address that matches your knowledge of the address then the address you entered is being validated as expected.
I’m sure you’ve encountered other examples. These are two simple scenarios I’ve run into recently – it typically works better in interviews if you give examples from your experience (with confidential information omitted, of course).
Q129. What interview questions can a fresh college graduate with no extensive experience can expect in an interview?
If I were interviewing a software tester, I’d be most interested in finding out their level of general computer knowledge. This is because the more experience and knowledge they have of computing in general, the more understanding they will have of how programs work and the potential problems to watch for. This knowledge is usually only cemented in someone who has an active interest in computers and spends a lot of their spare time using one. The person who only started using a computer in college or only uses one when they have to is not usually very knowledgeable about them.
To kick off I would ask general questions. Did they have a computer growing up, or frequently use one? Do they know what basic hardware components are in a computer and what their respective functions are? Do they understand what an operating system is? I would not hire someone who floundered about at this level.
If they are going to be testing internet applications, I would also check for some general knowledge about the Internet. What is DNS? What is a router? Do they understand client side (browser) versus server side processing? Lack of knowledge here wouldn’t be an automatic fail, but it would leave serious doubts in my mind.
I would gradually get more detailed in my questions, especially if the candidate expressed that they are experts or very knowledgeable in a certain area.
My third approach would be to test their problem solving skills. Your QA tester might not be fixing the bugs in the code, but the more they can narrow down the problem and identify the specific circumstances that trigger it, the faster and cheaper it will be for your developers to correct the bug. To do this I would present some sample problems and ask the candidate how they would proceed and report the bug. Presenting an actual live demo on a PC would be ideal, but hypotheticals would work as well.
And finally, I try and see how methodical the candidate is. The ideal candidate is going to approach testing methodically – he / she is going to be able to create a testing checklist / method which will cover all the important aspects of the program’s functionality thoroughly. This is a hard one to test for. You may pick it up while posing the hypothetical (or real) problems to the candidate, and watching carefully how they proceed.
If you are running the interview, and don’t really have good knowledge of the above areas, try and get someone who does to interview, or the smooth talking candidates will easily pull the wool over your eyes and impress you with their confident ignorance. If you are that potential candidate, and you know you are not very competent in any of the above areas, save yourself and any potential employers a lot of pain, and take some career aptitude tests to find your true career path.
Q130. Which testing we perform first Smoke or Sanity, Also what are difference between them?
Obviously we perform smoke testing first to test whether the build is ready for further details testing.
Sanity testing is done after bug fixing to verify whether the fixes works or not.
Lets have a look in details:
- Designed to touch every part of the application in a cursory way. It’s shallow and wide.
- Conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
- Focuses on one or a few areas of functionality. Usually narrow and deep.
- Usually tests specific functionality that was just added.
Q131. What is “bench-testing code”?
In short, it’s a synonym for unit test code.
I believe it originates from hardware design:
A hardware developer would create a device, then plug that device into a “test bench”, which would then run sample inputs and verify that the output on the pins of the device was correct. It was basically the first (automated) unit testing.
Flash forward to today, it’s a synonym for something that performs unit tests. A TestFixture class in Nunit is analagous to a test bench: You “plug” your class into the TestFixture, and it does its thing similar to how a physical test bench works for hardware.
Q132. Can you act like a normal, or non-experienced user?
(This seems silly, but it gives a very good insight. If the candidate says yes, quite frankly, they’re not what they appear to be. No person who works in the field of Information Technology in a development (in particular), analysis or test role can do this; simply for the fact that we are way past the level of an inexperienced user. The answer should be:)
No, however I can create test cases that can accurately map to a “so-called” normal users behavior.
Q133. What is the difference between Severity and Priority?
It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system. For example: If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.
Severity can be of following types:
Critical: The defect that results in the termination of the complete system or one or more component of the system and causes extensive corruption of the data. The failed function is unusable and there is no acceptable alternative method to achieve the required results then the severity will be stated as critical.
Major: The defect that results in the termination of the complete system or one or more component of the system and causes extensive corruption of the data. The failed function is unusable but there exists an acceptable alternative method to achieve the required results then the severity will be stated as major.
Moderate: The defect that does not result in the termination, but causes the system to produce incorrect, incomplete or inconsistent results then the severity will be stated as moderate.
Minor: The defect that does not result in the termination and does not damage the usability of the system and the desired results can be easily obtained by working around the defects then the severity is stated as minor.
Cosmetic: The defect that is related to the enhancement of the system where the changes are related to the look and field of the application then the severity is stated as cosmetic.
Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This priority status is set by the tester to the developer mentioning the time frame to fix the defect. If high priority is mentioned then the developer has to fix it at the earliest. The priority status is set based on the customer requirements. For example: If the company name is misspelled in the home page of the website, then the priority is high and severity is low to fix it.
Priority can be of following types:
Low: The defect is an irritant which should be repaired, but repair can be deferred until after more serious defect has been fixed.
Medium: The defect should be resolved in the normal course of development activities. It can wait until a new build or version is created.
High: The defect must be resolved as soon as possible because the defect is affecting the application or the product severely. The system cannot be used until the repair has been done.
Few very important scenarios related to the severity and priority which are asked during the interview:
High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system. (Eg. A site maintaining the student details, on saving record if it, doesn’t allow to save the record then this is high priority and high severity bug.)
High Priority & Low Severity: The spelling mistakes that happens on the cover page or heading or title of an application.
High Severity & Low Priority: An error which occurs on the functionality of the application (for which there is no workaround) and will not allow the user to use the system but on click of link which is rarely used by the end user.
Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report (Not on cover page, heading, title).
Some Specific Examples related to defects Priority and Severity:
In web application, if the Logo or the company name is not displayed fine, then its high severity and low priority issue. If in the application home page, if a link is not working then it’s a high priority but a low severity defect.
Priority is how soon the issue needs to be resolved. Severity defines the impact of the issue. Going by the question, it’s a high priority issue as it impact the branding of the image rather than affecting any functionality in the websites.
Priority should be set after discussion with the business (which is usually done by the functional tester) Severity is set after discussing with the dev team.
Suppose a Logo text is not proper that will be affect to company Work than that is a called High Severity and Low Priority.
High severity low priority: Logo of the company
High severity high priority: Submit button of login page not working or page not displaying
Low severity high priority : e.g.: if in a bike yourself start is not working but kick start is … it’s a high priority that u kick start also can stop but severity is low because for now you have an option to work with
Low severity low priority: spelling mistakes in text of home screen
Following is an example for high severity and low priority:
High severity: Affecting end user
Low priority: Typos
Note: Some of the above contents might be similar to contents in qaquestions.net. I am working on this to make the answers current and relevant.
More Interview Questions Coming Soon!!!!