INTERVIEW STARTER

Tell me about your last project I am working as a software tester since 2007 my first project was with guidance financial Since then I am working with solution one which a consulting company I have successfully Completed five projects for different client in my present job What if there is no software requirement? I will ask business analyst to walk me though the requirement. Where do you do the testing? We do the testing in the testing environment. What kind of testing you were doing? Mostly we do the front-end testing. Which place you feel comfortable during testing? I used to functional and user-acceptance

What were you responsible to test in your previous company? My responsibility included preparing and executing test case Understanding the Functional, Specification and Design documents, preparing the Requirement Traceability matrix, Report the bugs and Log the bugs in the Defect Tracker do smoke Testing to decide whether the application it is ready for testing and the major functionalities are working or not. Also, involve in Regression Testing. In my last project I was involved in manual testing we were working on a telecommunication application. We were involved in functional and User Acceptance Testing. My responsibility was to write and execute test cases. Tell me about your last application In my last project I was mainly involved in functional and user acceptance testing the application was a web base ecommerce application How testers report the bugs in manual testing? What bug tracking system did you use? Bugs are reported with the help of Bug Tracking tools .In reporting tool such as Quality Centre there is defect tracking module .The defect tracking working flow consist of add defects, review new defects, repair open defects, test new build, analyze defect data .Defect can be report with any tool and in excel sheets too. What is meant by Test Passes? How many passes are required for Integration testing? When expected result matched with the Actual outcome for the Test Steps then the status is defined as Passed. For Integration each Test Cycle needs a Pass status that is every Test Run/ Test Iteration needs a Passed status for the quality release. How will you trace the relation between test cases, requirements and defects? We can identify the relationship between Test Cases, Requirements and Defects using RTM.RTM is a technique used for gathering the requirements, which is called as requirement traceability matrix. Once all the requirements are gathered using the traceability method

mentioned, user can write test cases based on the gathered requirement and mapped these with the requirement which helps the user to know whether all the requirements are covered or not. Once user is assured that all the requirements are gathered. He/She can execute those test cases and on failing of any test cases he/she can map it with the associated test case, which is further mapped with the requirement. What is the difference between Testing Life Cycle and SDLC? Testing is a part of SDLC. SDLC include Requirements, Specification, Architecture, Design Implementation, Testing, Deployment, Maintenance.

What are the main elements of a test plan? A test plan is a document detailing a systematic approach to testing a system or software. The plan typically contains a detailed understanding of what the eventual workflow will be. A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by test lead. The main elements of test plan is Test plan identifier, Introduction, Test items, Features to be tested, Features not to be tested, Approach, Item pass/fail criteria, Suspension criteria and resumption requirements, Test deliverables, Testing tasks, Environmental needs, Responsibilities, Staffing and training needs, Schedule, Risks and contingencies, Approvals What is the minimum requirement to start testing? To Start Testing with a minimum requirements we need to look for the following availabilities: 1. SRS ( Software Requirements Specification) about the Project. 2. High level Test Cases defined as per the SRS including all the main functionalities. 3. Setting up the System environment as per the SRS. 4. Test plan and Test schedule should be created to do the Testing in a more effective way. 5. Skilled Testers/Human Resources to handle the Testing in a effective way.

How would you prioritise your test and why? Assigning priority in testing play vital role in testing Priority 1 - Critical/Fatal -- It should be fixed immediately Priority 2 - Major - It should be fixed before delivering to the customer priority 3 - Minor -- It should be fixed in the next module or omitted What is the most important thing in a test case? To prepare test cases depends on use cases we can follow below approach: Step 1: Collect responsible modules use cases Step 2: select a use case and their dependencies ( Dependent & Determinant ) Step 2-1: identify entry condition Step 2-2: identify input required Step 2-3: identify exit condition

Step 2-4: identify output / outcome Step2-5: study normal flow Step 2-6: study alternative flows and exceptions Step3: prepare list of test cases depends on above study Step 4: review test cases for completeness and correctness Explain difference between random testing and error guessing Random testing: A black box test design technique where test cases are selected possibly using a pseudo-random generation algorithm to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performance. Error guessing: A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made and to design tests specifically to expose them. In a Test Plan, the Features to be Tested and the Features not to be tested are generally included, is there any rationale behind why this should be or should not be included in a Test Plan? Or How do you determine what is to be tested? Every release will have a Scope. There will be some areas which will not be covered in the present build. So it is mentioned in the Test Plan that test cases which will cover those areas will not be tested. This will ease the test case preparation and avoid unnecessary work

What is the difference between usability testing & user acceptance testing? In usability testing tester verify the usability features provided by the application like easy to use easy to learn look and feel navigation help etc. which should attract the client and usability is a part of user acceptance testing. UAT (user acceptance testing) means the client users will conduct the Acceptance testing to verify whether the S.W is working according to their business requirement. Client not only checks the requirement but also usability features. What is smoke testing? Smoke testing is the initial testing when we get the Build. In this testing we test whether the build is Stable to execute the test cases in the next phase of testing. If we find any major functionality is not working then we reject the build. If all major functionalities are working properly then we accept the build for comprehensive testing. This can be called as Build Verification testing. What is the final Stage of Integration Testing? The final stage of integration testing is to combine all software components (or modules) into an organized meaningful whole and perform system testing to verify all pieces work properly in concert with one another. Is the Static testing a functional testing?

Static Testing It is a type of unconventional testing i.e. testing performed on an application when it is not executed. Ex: GUI Testing, Document testing Static Testing is not a functional testing. Static testing is also called Verification. Can the static testing be done for both Web & Client Server Application? Static testing doesn't depend upon the application so we can do static testing on web or client server application. Why is testing done? Why does QC perform testing? How if testing diff from Internal Review and peer level revew? When to stop testing? Testing is done to ensure the software product is reasonably bug free and satisfies the requirements specified. QC conducts only inspections and audits to check the work product is as per the quality standards. 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 What are the difference steps followed for web based and windows based application in manual testing? What In Web application we should check additional cases that you don't use in windows application such: 1. Checking the application in all Internet Explorer version (or from version that your application should support until the last version) 2. Fire Fox browser (in case that your application should support) 3. Netsape browser (in case that your application should support) 4. All Windows platforms ( Win95 + Win98 +.... - or from version that your application should support until the last version + Service Pack versions) 5. Checking your application with Internet Options 6. Checking your application with different windows resolution and settings Is retesting is regression testing or its a part of regression? Regression Testing: When a bug is found in an application then that bug is reported to developers. They apply modifications (Regress) on it and send back to tester. Tester again check the application & see if it is working correctly now or not i.e. when any modification is made to an application testing is done to check whether it is working fine or not called regression testing. Re-Testing: Testing done by applying different values to a module to see its desired functionality. At what stage the unit testing has to be done? When the coding part for the current module in the present build has been completed and before releasing the build to Integration test, Unit Testing has to be done. Once the individual modules are completed, then those code modules will be tested individually in Unit testing to ensure that the inner working of the code is working properly. Usually by Done by programmers in many companys. In some companys testers will also do unit testing. What is Defect Density and how can we calculate Defect Density ?

Defect density is a measure of the total known defects divided by the size of the software entity being measured. Number of Known Defects --------------------------------Size The Number of Known Defects is the count of total defects identified against a particular software entity during a particular time period. Examples include: Defect to date since the creation of module Defects found in a program during an inspection Defects to date since the shipment of a release to the customer Size is a normalizer that allows comparisons between different software entities (i.e. modules releases products). Size is typically counted either in Lines of Code or Function Points. Uses: Defect Density is used to compare the relative number of defects in various software components. This helps identify candidates for additional inspection or testing or for possible reengineering or replacement. What is path coverage? Path Coverage or Basic Paths Coverage is a white-box testing technique. In this coverage the programmer runs the program so as to cover every statement of the program. Following steps are involved in this 1. Draw a flow graph to indicate corresponding logic in the program. 2. Calculate individual paths in the flow graph. 3. Run the program in all possible ways to cover every statement. What are the docs required for Performance Testing? Performance testing is used to determine the speed or effectiveness of the application. The main document is SRS. Performance testing is also same as other here we have to see to how many user's our application can feed up request at one time how minimum resources it required to work how it behave when it is under stress. What is usage of spiral model? Spiral model is used for high risky projects. Here we make a part verify that then do enhancements and again verify and so on up to completion of project. What is meant by CRS & URS explain briefly? CRS: Client Requirement Specification Here requirements are gathered up on Client points. URS: User Requirement Specification. Here requirements are gathered up on End User points. Which testing methodologies have you used in your project and what different methodologies do you know Some commonly used software testing methodologies are Waterfall model, V model, spiral model, RUP, Agile model and RAD.

How many pages test strategy did you write? Test lead write test strategy typically the test strategy includes 1) Environment requirements ,2) Test tool requirements, 3) Risks and mitigation, 4) Roles and responsibilities, 5) Schedule, 6) Regression approach, 7) Test priority assignment criteria, 8) Entry and exit criteria, 9) Test results and status reporting You are 5 testers in a team and got the requirements. What you will do? If the testing team size is 5 then the specification will be divide in to equal parts and each every team member in the testing team will be allocated a separate part of the specification After all the testing has been done, what will be the next? After all testing is done then we can provide the sign off. After that we should prepare Exit document. Have you written any test cases that didn't run? If the requirements changes rapidly during the project than there is changes that the test case is not run i dont remember such situation Unit testing comes under which testing technique? 1. white box testing technique2.black box testing technique Unit Testing comes under White Box Technique. Developers do the unit testing.. Define quality in testing Quality in Testing- The application functions as per the Customer's requirement. Whats containing on the test strategy? Test Strategy is the approach to be followed for testing the software. It contains scope and objective, business issues, responsibility matrix, roles and responsibilities, communication and status reporting, testing automation and testing tools and defect. What is Thinktime? What is Prevention Testing? Thinktime: The time to create request by the client to send to server is called Think time. Prevention Testing: Build test cases based upon the requirements specification error to the creation of code with the express purpose of validating the requirements. If an application has 100 pages to be tested. How much time it will take?How u caluculate? This depends upon the complexity of the pages. May be one page will be having only the content and other page having very complex financial calculations. The easy way of finding the time is to find the time of development of these individual pages. And calculate 30-40 time of testing as per the time consumed in developement.

What do u mean by Masked Defect An occurrence in which one defect prevents the detection of another is defect masking. So the undetected defect is masked defect. How can you take snapshot/screen shots in case of manual testing and how can you attach it to the test print screen button and paste it
Press and hold the fn key (located to the left of your spacebar) and then press the insert/prt sc key (usually just above the backspace key.) This saves the Screenshot to your clipboard. Then paste it.

Can you please explain these different approaches of testing a distributed system to me?Simulation-based-What is difference between Integration testing & Inter system testing? Integration Testing: integrate the all modules and test whether it is functioning correctly or not. Inter system Testing: testing whether our application/software is supporting the existing software or OS. How will you know whether your reported defect accepted are rejected? From status changed by the developer tester will understand his defect has been accepted or rejected. What is entry and exit criteria of a test plan? Entrance criteria for testing are when the Software Requirement Specification document is complete. Exit Criteria for testing is not fix the exit criteria depend upon factors like Dead Line to deliver the software, all the test cases written are complete, budget is complete, major error prone areas testing are complete. What is error feeding? Error feeding: The process of intentionally adding known faults to those already in the application for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program. In a company if you don't have hard core written System requirements and the product keep on changing, new features are added without testers knowledge ,in such situation how do you test application? Such situations would normally not arise if a company follows certain standards to maintain quality. Mostly after a certain stage the requirements are locked they cannot undergo future requirements. In case a company does not follow such standard in that case the customer needs to be highly flexible so does the scheduled date of release of the product needs to be flexible

At what stage of Software development life cycle we can start writing Master Test Plan? Is it Testing Test plan should start at requirement stage. What is the difference between system testing and functional testing? The functionality testing we will concentrate only about that particular functionality in the application without bothering how it works in actual environment where as in system testing we will consternate on what is the role of that functionality in whole application.2) We can't test the performance of the application in functional testing but in system testing we can.3)Generally we will use functional specification to test the functionality of our application where as in system testing we will use SRS or BRS What is grey box testing? Grey box testing is a combination of black box and white box testing. It is usually done by the developer during the coding phase to test whether a particular functionality works as per requirement against the code coded by him using a combination of black box and white box testing techniques. In an application currently in production, one module of code is being modified. Is it necessary to re- test the whole application or is it enough to just test functionality associated with that module? 1) Test the modified module 2) Test all the other modules/areas of the application which will have direct/indirect interaction with the modified module. What is the difference between bug priority & bug severity?
Priority tells U how important the bug is. Severity tells U how bad the bug is. Severity is constant....whereas priority might change according to schedule.

How would you conduct your test To conduct my test, I would follow these steps (which vary between industry, company, and projects): 1) Understand its business requirements 2) Understand its technical specifications 3) Perhaps call it out in a test plan to determine how cross-functional experts feel about it 4) Ensure the test environment and test tools are set up properly to test it 5) Create test case(s) for it 6) Map its test case(s) to requirements 7) Execute its tests and report defects 8) If defects are found, re-test them when they are fixed 9) Close the issue when test passes

What version of OS were you using?

Windows 98, Windows server 2003, window Vista and XP. What is a test script and test condition? Test Case Definition: A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement A test case is a document which explains the action performed in particular application and group of test cases is called as test script What the things that you need to do after the bug is fixed and before it come for Retesting? How you will make prepare for this scenario? How do analyze the risk for the web application project? Looking for answer What is the test approach, test case and test scenarios to use in testing an online eCommerce site? The test approch should be 1) GUI Testing 2) Smoke testing 3) Functional Testing security testing etc. 4) Retesting and Regresstion testing' 5) Confirmation Testing 6) UAT In case of online e Commerce Site first of all find out the positive and negative scenarios. According to the scenarios write down the test cases consideration with the test types. Please let me know if I am wrong anywhere. Which tool is ideal for website testing in which performance, response time and functionality is required to be tested? loadrunner and jmeter How will you perform testing font and alignments in a web site manually?

How will you test cookies in web testing Its clearly depends up on the Requirement. Cookies is the file where the user informations are stored up on suitable time limit. To Test cookies ensure that 1.) Login Details are remembered at the next login (userid & pwd field should be pre-pouplate up on request at first login) 2.) Depends up on the user(s) information should stored. 3.) Check the Cookies(Sesion Identification) expiry time and should be noticed on execution. 4.) Check the Cookies session end once the IP address is changed or to change. 5.) Never the same Cookie session will not be work on different IP address

What severe bug you raised while testing a web application which you are proud of?

What are all the test cases you will execute for compatability testing with different browzers?
How you can calculate the session time? For our application one global setting is defined with the time, if the time is 1 min, system is idle for 1 min then current session should be timed out. Calculating the time means we can calculate using stop watch. How to test the interface? Testing can follow below steps. Open the application and observe the session timed out time set in the system put the system in idle stage up to reaching the session timed out. Again try to invoke the application If the current session is time out then ok or else need to raise the issue Describe procedure to conduct load,stress,compatibility,security testing for web-based application?

Load: It's depends on no.of users ie how many users can access the application and mean while application should not be crashed, it can be done using automation tool like Load runner. Here we can create the virtual users. For ex, client wants 300 users capacity of his application then we need to create more than 300 virtual users and start working on load runner, if still application works well then no problem or else need to raise the issue. Stress: It's depends on no.of clicks on the button/application, for ex: there is a button in application page 'Submit', if users keep on clicking on submit button then application needs to handle this situation in a better way, if it's responds in ri8 way then no pb, or else need to raise an issue. Compativility : This can be done using diff environments , for ex: one application is developed in IE and this should be behave as same as how it behaves in IE when user invokes in Mozilla, if not need to raise an issue Security: This is a big process, there are so many types of testing, we follow below ones XSS : Try to enter simple XML functions into all editable fields and verify whether it has vulnerability or not. Ex: <script>alert ('XSS');</script> Buffer over flow: Try to enter data morethan the length of the field into all editable fields and observe the application thrown the concerned validation messages or not. SQL injection: Try to enter hackable sql queries into all editable fields and observe user is able to logged into system or not, if logged in then need to raise issue. syntax: use this while checking the user id " testuser10' or 1=1 " CGI Parameters: Although hidden form fields are a good way of passing data between pages, there is a big drawback in using this method: The user has to submit a form to an "action handler," usually by pressing a button. It may seem like a small point, but users are more used to clicking on hyperlinks or images for their navigation than form Submit buttons. URL Jumping: Try to invoke the next stage by passing the current step, for example while doing online transaction there would be 3 stages, 1st stage contains the credit card verification, if user by passes the first stage then he can do the transaction successfully, if he done like this need to raise the issue.
What factors are considered when we perform usability testing of web application? What is the most important testing which we consider when we test a web application?

Usability testing is done for" user friendliness". In this we check how comfortable the customer is in going thru the application. suppose for an example while logging in he forgot his password, in usability testing u have to check whether there is an "forgot password option" and if we click this it is asking for secret question or not and many things u can test like there should be minimise and maxmise button for a window....and so on

Can anyone explain me about web services testing?

In web testing we just see whether the concept (functionality) of web services is working or not. Can we test a web application in offline mode? We can test a web application in offline mode For this we have to configure the same site on the local machine and then carry out testing in offline mode, and need to have the web server, database server (if required) in your local machine. Now we can start our natural testing.

What are some test cases for testing a search engine website e.g google Verify that google default search page is invoked or not http://www.google.com Enter a valid word ( which should have some sites) into google search word and submit the page Ex: google Verify the results are really related to give word or not Observe the multi languages links are shown or not Below options should be shown Advanced Search Preferences Language Tools Verify the results for a semi correct word Ex: google is a ri8 word, goglle is semi correct word and it should nt have results, in this situation below message should auto populate automatically. Ex: Did you mean: google By clicking on above link it should again refresh the search criteria If search result crosses more than 10 sites then below link should show What is requirement traceability matrix A traceability matrix is a document that correlates any two baseline documents that require a many to many relationship to determine the completeness of the relationship. It is often used with high-level requirements (these often consist of marketing requirements) and detailed requirements of the software product to the matching parts of high-level design, detailed design, test plan, and test cases. A requirements traceability matrix may be used to check to see if the current project requirements are being met, and to help in the creation of a Request for Proposal, various deliverable documents, and project plan tasks. Common usage is to take the identifier for each of the items of one document and place them in the left column. The identifiers for the other document are placed across the top row. When an item in the left column is related to an item across the top, a mark is placed in the intersecting cell. The number of relationships are added up for each row and each column. This value indicates the mapping of the two items. Zero values indicate that no relationship exists. It must be determined if one must be made. Large values imply that the relationship is too complex and should be simplified. To ease the creation of traceability matrices, it is advisable to add the relationships to the source documents for both backward traceability and forward traceability. In other words, when an item is changed in one base lined document, it's easy to see what needs to be changed in the other. If you are hiring a tester what quality you are looking for Tester should have strong communication skills. Tester also needs to have a Can Do Attitude and a keen eye towards finding bugs.

What are the various error we get while requesting for a web page ? 1. Server timeout errors 2. Page not found errors 3. Unhandled Exceptions

404 html error code : When the page requested is not available or the page is removed or the user has typed in a wrong url. usually it is client side error 500 series html error code : When the server is down or the server encountered some problem when the client request came in. It is usually a Server side issue Browser compatibility Testing . Alignment issues on different web pages 2. Security Certificate errors - and other script errors Content Mismatch 2.Inappropriate Response