QA interview Questions

Tell me about the worst boss you have ever had.

(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 form 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.

how to drag an drop?

(new Actions(driver)).dragAndDrop(element, target).perform();

what does the SDLC include?

1. Requirement phase 2. Design phase 3. Coding (programming) 4. Testing 5. Release (Production) 6. Maintenance (Support)

What are different types of software testing?

1. Unit testing. 2. Shakeout testing 3. Smoke testing 4. Functional testing 5. Integration testing 6. Regression testing 7. System testing 8. Load testing 9. Stress testing 10. Performance testing 11. User acceptance testing 12. Black box testing 13. White box testing 14. Alpha testing 15. Beta testing

What do you do once you find a defect?

1.Recreate the defect-one 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 screenshot-(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. Fro instance, let us day that instead of "continue" button on a page, there is a typo "continue" button on a page, there is a type "Contiinuee". Now , we will make a screen shot of this page 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 rationale Clear Quest, or JIRA, some use PVC tracker and so on.) Now a tester needs to write defects in easy and clear language to make all the developers to understand easily.

what does test plan 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.

What is a Use Case and what does include?

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, Floe of Events ( normal flow and alternative flow), Exceptions, Special Requirements, Pre- conditions and Post -conditions.

what is a "bug"?

A bug is an error, flaw, mistake, failure, or fault in a computer code (program) that prevents it from behaving as intended (producing an incorrect result). (You can also add this :When the expected results (accordingly to the requirement documents) do not match with the actual results (while testing), then it is considered a bug)

What is a module?

A module is a software component that has a specific task. It can be a link which can go inside to its component detail.

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

A small test 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.

What does Test Case includes?

A test Case includes Test Case ID, Steps description, expected output, actual output, pass/fail, remarks.

What is Test Case?

A test case is a document the descries step by step process how to test the application.

what is test plan?

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 is Test Strategy?

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 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.

Explain Bug Life Cycle

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 bugs 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 no then the test will reopen it and same cycle starts.

Can you tell me what a Use Case is?

A use case is a document that describes the user action and system response for a particular functionality. ( you can also include, for example, in the Use Case given below, is a Use Case for login system for a company called Auto Parts One. This application is being developed by Digital Systems, Inc. The project name is Auto Parts One. However, the business owner (user) is a company called American Auto Parts of the North (imaginary name)

What is acceptance testing?

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.

What is index in SQL?

An index is used to speed up searching in the database. An index can be used to efficiently find all row matching some column in your query and then walk through only that subset of the table to find exact matches. If you don't have indexes on any column in the WHERE clause, the SQL server have to walk through the whole table and check every row to see if it matches, which may be a slow operation on big tables. The index can also be a UNIQUE index, which means that you cannot have duplicate values in that column, or a PRIMARY KEY which in some storage engines defines where in the database file the value is stored.

What is an inspection?

An inspection is a formal meeting, more formalized than a walk through and typically consists of 3 to 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 inspections 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.

Can you tell me about yourself?

Answer: In my QA career, I have been working on various system platforms and operating systems like Windows 95, Windows 2000, Windows XP and UNIX. I have tested applications developed in Java, C++, Visual Basic 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 worked in different databases like Oracle and DB2, wrote SQL queries to retrieve data from the database. file:///F|/intervew%20questions/Interview%20Questions%20for%20QA%20Tester.htm[8/17/2012 2:31:07 AM] Interview Questions for QA Tester 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 ClearQuest and TestDirector. Once the defects were fixed, retested them and if the passed, closed them. If the defects were not fixed, then reopened them. 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.

what is difference between Load testing and performance Testing?

Basically, Load Stress and performance testing are the same. however, load testing is 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.

What is meant by walk thru meeting?

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.

what is comparison testing?

Comparison testing is testing that compares software weaknesses and strengths to those of competitors' products.

What is compatibility testing?

Compatibility testing is testing how well software performs in a particular hardware, software, operating system, or network environment.

what is data?

Data is number, character or image which has some information.

Difference between delete, drop, truncate in SQL

Delete: remove rows in table, and after that have to commit(confirm) or rollback(cancel), can use where to specify which row to delete. Truncate removes all removes all rows that make table empty. can not specify which row to delete.The operation cannot be rolled back and no triggers will be fired, the table structure still remain. drop table delete the table from database, even if delete the structure.

What is the role of documentation in QA?

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.

What testing approaches can you tell me about?

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-hock testing, User acceptance testing, Comparison testing, Alpha testing, Beta testing mutation testing.

How do you know it is sufficient testing?

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.

How do you execute testes?

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 not 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 outputs 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 discrpancies/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 buts/defects uncovered during testing. A pass/fall criteria is used to determine the severity of a problem, and results are recorded in 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 mitigated 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.

how to determine what to test in an application?

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.

Let us say you have a web application to test. How do you go about testing it? What is the process?

First of all, I will look at the requirement documents (or design document is 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 and application.

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

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 of 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.

How to click on hidden element in Selenium WebDriver?

First store that element in object, let's say element and then write following code to click on that hidden element: JavascriptExecutor js = (JavascriptExecutor)driver; js.executeScript("arguments[0].click();", element);

What are the different tests that can be done for Client Server Application and Web-Based application. Give details.

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 5.0, 6.0, 7.0), Firefox, Safari (for Mac) and so on where as for client server, we do not need to test in the browser.

What kind of challenge did you have when using page objective model?

High Setup Time & Effort. It takes more time compare to other models.

Are you better working in a team or working alone?

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.)

What made you to choose testing career?

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.

From you resume, I see that you have been working in one place for a very short period of time. This raises me questions why? can you explain why?

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.

What problem did you face in the past? How did you solve it?

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) Defect 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 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 lo 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 on each 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 our that in one of the table, the data was not recorder. In all the table (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 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 in to pdf format. Once the document was uploaded, I saw that the fields in the pdf docuement were interchanged (misplaced). for example, the First Name displayed in the Last Name section. Data 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 hade 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 heep://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 and 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 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 Data of Birth was missing in the PDF file.

How do you write Integration test cases?

I have never write 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 works 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.

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

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 send to 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 manipulated 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 report, 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 report is next job.) then I had to run diffent jobs in the ETL system. Once we run the job, the running job finally crates an outpu file which is now validated by Nix. (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 ->to see the contents page by page cat->list contents of the file chmod->change permission cp -> copy rm->delete a file

Why do you like this job?

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 involve 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.

where do you see yourself in another 5 years?

I see myself a QA lead in another 5 years.

How can you be sure that the query you wrote is correct? Or how do you know that the data you pulled from the database is correct.

I write SQL query based on the requirement document. In the requirement document, various conditions are given for the query. Base on those conditions, I write SQL query. therefore, anything different from the requirement document is definitely a defect.

How many test cases did you write in your last project?

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)

What will you do if developer does not accept the bug?

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 document, both tester and developer will have to look at the requirement document, validate it and then reopen it if necessary or close.

How can software QA processes be implemented without stifling productivity?

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. Problems prevention will lessen the need for problem detection. Panics and burnout will decreasing and there will be improved focus an less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based process 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 should be that more days of planning and development will be need, but less time will be required for lat-night bug fixing and calming of irate customers.

difference between implicit wait, explicit wait, and fluent wait?

Implicit Wait: During Implicit wait if the Web Driver cannot find it immediately because of its availability, it will keep polling the DOM to get the element. If the element is not available within the specified Time an NoSuchElementException will be raised. The default setting si zero once we set a time, the web driver waits for the period of the Web Driver object instance. Explicit Wait: There can be instance when a particular element takes more than a minute to load. In that case you definitely not like to set a huge time to Implicit wait, as if you do this your browser will going to wait for the same time for every element. Fluent Wait: Let's say you have an element which sometime appears in just 1 second and some time it takes minutes to appear. In that case it is better to use fluent wait, as this will try to find element again and again until it find it or until the final timer runs out.

What is unique key in SQL?

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.

what is Primary key in SQL?

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.

What did you do in your last project?

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.

What is Test Harness?

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 configurations and monitor its behavior and outputs. It has two main parts: the test execution engine and the test script repository.

what if software too buggy, it cannot be tested at all?

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.

Stress testing

In this type of testing the application 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.

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.

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.

Alpha Testing

In this type of testing, the users are invited at the development center where they use the application and the developers note the 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.

What does Test Strategy include?

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.

What is Business Requirement Document (BRD)?

It is a document that describes the details of the application functionalities which is required by the user. this documents is written by the business analysts.

What is Unit testing?

It is a test to check the code whether it is properly working or not as per the requirement. It is done b the developer not tester.

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.

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.

Integration testing

It is a test to check whether all the modules are combined together or not and working successfully as specified int the requirement document.

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.

What is Back-end Testing?

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.

smoke testing?

It is an initial set of test to check whether the major functionalities 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.(Software Quality Assurance tester)

What is database?

It is collection of logically related data designed in a tabular form to meet the information needs of one or more users.

What is change control (Or Change Request)?

It is document that describes the additional functionalities 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 field. 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.))

how to decide what to automate?

It is impossible to automate all testing, so it is important to determine what test cases should be automated first. the benefit of automated testing is linked to how many times a given test can be repeated. Tests that are only performed a few times are better left for manual testing. Good test cases for automation are ones that are run frequently and require large amounts of data to perform the same action. You can get the most benefit out of your automated testing efforts by automating: 1. Repetitive tests that run multiple builds. 2. Tests that tend to cause human error. 3. Tests that require multiple data sets. 4. Frequently used functionality that introduces high risk conditions. 5. Test that are impossible to perform manually. 6. Test that run several different hardware or software platform and configurations. 7. Tests that take a lot of effort and time when manual testing

white box testing

It is test where a tester looks into the code and performs the testing.

Black box testing

It is test where a tester performs testing without looking into the code. Or A testing mehod 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 know as behavioral testing, since only the external behavior of the program is evaluated and analyzed.

What is business Design Document?

It is the document which descirbes the application functionalities 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.

What if the application has functionality that was not in the requirements?

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 is not 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.

How to deal with your team members?

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. Do not worry. Do not 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, do not 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.

Do you have any situations in the past where you have some argument with your team member?

No. I never had that type of situation wherever I have worked. (even if you had one, it is a good to say "NO". This could be a red flag, which might stop you form getting the job).

Are Test plan and Test Strategy same type of document?

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.

who do you ask?

Now Let's say you did not understand something while reading documents. who are you going to ask? Business analysts who wrote this document. If you have any other questions that you do not know you will be asking that you friend first, if he 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 question 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 do you do on our first day of the work?

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.

What do you do if you have any questions to ask?

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 (Do not 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 website and give it to them. you will be hero.)

What is software testing methodology?

One software testing methodology is the use a three step process of 1. Creating a test strategy. 2. Creating a test plan 3. executing test. This methodology can be used and molded to your organization's needs.

How to clean cookies?

Open the menu, click tools -> internet options -> click delete button, and click delete. By code driver= new FirefoxDriver(); String URL="http://www.flipcart.com"; driver.navigate().to(URL); driver.manage().deleteAllCookies();

What is parallel/audit testing?

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.

what is recovery/error testing?

Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

How to write Regression test cases?What are the criteria?

Regression test cases are also base 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.

What document did you refer to write the test Cases?

Requirement document. (Note: It can also be use cases, or design document) it depends 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).

What is SQL?

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 programs like MS access, DB2, Informix, MS SQL sever, Oracle, Sybase, etc.

what is security penetrating testing?

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.

What are the basic commands in SQL +?

Select, update, create table,insert into, delete from, replace, truncate, where, and or, in, between, wildcard( _ for one charactor, % for any charactor), like, order by, gourp by, having, alias, as, joins,

What are the basic elements you put in a defect?

Severity, Priority, created by, version number, header, description of the defect where we write how to create a defect, in what module the defect is found, status, and so on.

Which testing are not done by QA tester?

Shakeout out testing (CMT)and Unit testing(developer) which are done by CMT (Configuration management team) and developer.

what is end to end testing?

Similar to system testing, the macro end of teh test scale is testing a complete application in a situation that mimics real world use. such as interaction with a database, using network communication, or interacting with other hardware application, or system.

What if there is not enough time for through testing?

Since it is 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 mos 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 where developed in rush or panic mode? 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 tests could easily cover multiple functionalities? which tests will have the best high-risk-coverage to time-required ration?

what is system testing?

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 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 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.

How do you crate a test plan/design?

Test scenarios and 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..

How do you derive test scenarios and use cases? What are the contents and format?

Test scenarios are derived form 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.

What is negative testing?

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' 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.

System testing

Testing which is based on overall requirements specification and it covers all combined parts of t a system. It is also a black box type of testing.

What was the process of QA testing in your company where you worked for the last time? (or As far as the QA process is involved, what was the testing process in your company?)

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.

What are all the basic elements in a defect report?

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 defet was found and so on.

What do you like about QA?

The best thing I like about QA is, I like the job which is more process oriented. For example, we have to work right form 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.

what do you like about a manager? and what do not you like?

The best thing I like about a Manager is that the

what does Test Strategy include?

The following are some of the component that the Test Strategy includes: 1. Test Levels. 2. Roles and Responsibilities. 3. Environment Requirements. 4. Testing Tools. 5. Risks and Mitigation. 6. Test Schedule. 7. Regression Test approach. 8. Test Groups. 9. Test Priorities. 10. Test Status Collections and Reporting. 11. Test Records Maintenance 12. Requirements tractability matrix 13. Test Summary

what is the general testing process?

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.

what i software development life cycle?

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.

How do you create a test strategy?

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 tests, 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.

What is a test/QA team lead?

The test/QA team lead coordinates the testing activity, communicates testing status to management and manages the test team.

How would you ensure that you have covered 100% testing?

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.

What is Software Testing Life Cycle (STLC)?

The testing of software has its own life cycle. It start with study and analyzing the requirements. Here is the software testing life cycle process. 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

What are the different matrices that you follow?

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) Tractability Matrix(also called RTM (Requirement Tractability Matrix) report - the document which shows the relationship between the functionalities or the business rules and the test cases. So, with the help of Tractability Matrix we make sure that we includes all the functionalities in our test cases according to the requirement document.

how do you make sure that it is quality software?

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 maybe 1 low defect)

How do you know when do you stop testing?

This can be difficult to determine. Many modern software applications are so complex and such an interdependent environment, that complete testing can never be done. Common factors in when to stop are Deadline (release deadline, testing deadline e.g.) 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; Beta or alpha testing period ends.

Shakeout testing?

This test is basically carried out to check the networking facility, database connectivity and integration of modules. (It is done by the Configuration Team)

What is the difference between verification and validation?

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.. Are we building the product right? 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. Are we building the right product?

Where do you write SQL query?

We Write SQL queries using some these tools: Todd Squirrel and Rapid SQL.

What are the types of test cases that you write?

We write test cases for smoke testing, integration testing, functional testing, regression testing, load testing, stress testing, system testing and so on.

If you have no documentation about the product, how do you test an application? describe the process.

Well this is 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 sometimes 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.

As a QA Tester, can you tell me the situation when you felt the most proud of it?

When I find the defect that normally others do not 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.

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.

What is Build?

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 the other word, the developer 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.

what is meant by the build deployment?

When the Build so prepared by the CMT is sent to different Test Environments, it is called the Build Deployment.

When you log a defect using TestDirector or ClearQuest what field you see?

When we log a defect, we see defect ID, Summary (where we write short description of the defect), Description (Long description of the defect), Detected by (person who found the defect), Severity ( meaning is the defect critical?), Date, Detected in version, Priority, Project, Status, Assigned to,

what can you done if requirement are changing continuously?

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. 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.

What is XML?

XML - Extensible Markup Language XML - is a markup language much like HTML XML 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.

Do you really need to write SQL as a QA Engineer?

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.

Have you done any Back End Testing and/or if you did, how did you do it in your last project?

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 banks 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 afterward batch-processed into the DATABASE in xml format. then the batch-processed data is sent to ETL (Extract-tranform load) which processes the job to create a file to produce the report. The files 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 back-end testing.

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?

Yes, I have been to thak kind of scenarios several times. there were companies where they had no documents at all. In this case, I had to discuss the application scenario and functionalities with the business Analysts or developer. I kind of prepared a document in consultation with Business Analysis and developer an then started writing Test Cases.

Have you worked with the Uses Cases before?

Yes, I have written Test Cases using Use Cases.

Is there a format for a test case? Do you follow any methodology for numbering test cases?

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. 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 case like "REQ-LOG-001-001" and so on.

Does a tester have to know about cookie?

Yes, a tester has to know How to clean cookies (Does not have to know the difinition)

Have you used automation tools?

Yes. I have used Jira as defect tracking tools. (Your answer is based on whether you have used automation tolls 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 tolls, 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 the stuff. But, since there is not much to learn in ClearQuest and TestDirector, you only have to know what different types of fields are there in the defect logging window when writing a defect.)

Have you written Change Control?

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 int he requirement document. Int he 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 functionalities on the other pages. Therefore, it was a consistency issue. I reported this as bug. But the project manager asked me to write it a 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 Change control. However, it is Not a job of a tester to write change control. it's the business analyst's job.

Why are you in QA?

because I like this job.

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.

give me five common problems that occur during software development.

poorly written requirement, unrealistic schedules, inadequate testing, adding new features after development is underway and poor communication. Requirements are poorly written when requirements are unclear, incomplete, to 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 do not know what is needed, or customers have unrealistic expectations and therefore problems are guaranteed.

what is most common syntax you have used while writing SQL query?

select.

How to write User Acceptance Test plan and test cases?

the way of writing test Plan and Test Cases is the same in all 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).

what is biggest bug you have ever found?

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 (pup 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) is not mentioned in the test case, I just wanted to try how to application reacts when Alt+F4 is pressed. Then I pressed Alt+F4. The result was a disaster. the application crashed. 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 temporary solution and the application went into production.

when should testing start in a project? why?

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) s set up and ready -When the manager asks us to go ahead and start testing.