Manual Testing Interview QnA Prepared by Kiran,thats ME!!!
1)Have 1)Have you ever completely tested any a ny part of a product? How? A1) One cannot do 100 % testing and say that the product is bug free. Below points should be noted: 1. Prepare tracebility matrix so that you wil know if any test case/ functionality is missed out By this you would know how far you have tested. 2. Also, make sure that you y ou have covered critical, complex functionality And there are no showstopper, critical bugs , major bugs. A2) It atually depends on the number of modules present in the product. If its less in number and have sufficent time and resource available for test -we can test the product completely. And if the product is many module .it become exhaustive for testing it completely in this case.We can test major funcitionalities of the application which are most visible to user and critical parts in the product.
2) What are the key challenges of testing? A1) Following are some challenges while testing software 1.Requirements 1.Requirements are not freezed. 2.Application 2.Application is not testable. 3. Ego problems. 4. Defect in defect tracking system 5.Miscommunication 5.Miscommunication or no Communication 6.Bug in software development tools. 7. Time pressures
3) What is the difference b/w system testing and functional testing? A1) 1)Functional Testing:-It is one of the testing type and related to functionality of system or component that 'What it does'. It focuses on suitability, interoperability, interoperability, security, accuracy and compliance. 2) System testing:- It is one of the test level and concerned with the behavior of the whole system/product as defined by the scope of a development project or product, it is
process of testing an integrated system to verify that it meets specified requirements. System testing should investigate both functional and non-functional non-functional requirements of the system.
4) When should testing be stopped? A) When the test manager is confident that the application will perform as expected in the production environment. This confidence is d erived by analysis conducted on: a) Deadlines (release deadlines, testing deadlines, etc.) are met b) Test cases completed with certain percentage passed c) Test budget depleted d) Coverage of code/functionality/requirement code/functionality/requirements s reaches a specified point e) Meantime between failures f)Risks associated with continuing to test g) Percentage of coverage achieved h) Number of open defects and their severity i)Risk associated with move to production
5) Describe to me when you would consider employing a failure mode and effect analysis. A) failure: failure means "the fact of somenthing expected not being done." that means the application peforms actions against the requirements. effect means " a change caused by mething" effect analysis: since application not perform a ctions according to the requirements re quirements we have to analyse the effect. i.e; where the application deviates from it's requirements and cause for that one.
6) What is the difference between System Testing and End-To-End Testing? Give at least 2 Examples. A) system testing : It is collection of testing types. Once the total application is developed, It is d eployed into the clients specific environment. If one performs testing to check is it working fine in all aspects of that specific environment is known as system testing. End-to-end testing: To check all internal components successful respond. like client,network,apllication client,network,apllication server, data base and etc...
process of testing an integrated system to verify that it meets specified requirements. System testing should investigate both functional and non-functional non-functional requirements of the system.
4) When should testing be stopped? A) When the test manager is confident that the application will perform as expected in the production environment. This confidence is d erived by analysis conducted on: a) Deadlines (release deadlines, testing deadlines, etc.) are met b) Test cases completed with certain percentage passed c) Test budget depleted d) Coverage of code/functionality/requirement code/functionality/requirements s reaches a specified point e) Meantime between failures f)Risks associated with continuing to test g) Percentage of coverage achieved h) Number of open defects and their severity i)Risk associated with move to production
5) Describe to me when you would consider employing a failure mode and effect analysis. A) failure: failure means "the fact of somenthing expected not being done." that means the application peforms actions against the requirements. effect means " a change caused by mething" effect analysis: since application not perform a ctions according to the requirements re quirements we have to analyse the effect. i.e; where the application deviates from it's requirements and cause for that one.
6) What is the difference between System Testing and End-To-End Testing? Give at least 2 Examples. A) system testing : It is collection of testing types. Once the total application is developed, It is d eployed into the clients specific environment. If one performs testing to check is it working fine in all aspects of that specific environment is known as system testing. End-to-end testing: To check all internal components successful respond. like client,network,apllication client,network,apllication server, data base and etc...
Or In other words, this testing is meant m eant for checking the inter operability of internal components for successful respond.
7) What are the th e roles of glass-box and black-box testing tools? A) Black-box testing: It is not based b ased on knowledge of internal design or code. Tests are based on requirements and functionality. Black box testing is used to find the errors in the following 1) Interface errors 2) Performance errors 3) Initialization errors 4) Incorrect or missing functionality 5) Errors while accessing external e xternal database Glass-box testing: It is based on internal design of a n application code.Tests are based on path coverage,branch coverage,statement coverage,statement coverage. It is also known as White Box testing. White box test cases can check for.. 1) All independent paths with in a modules are executed atleast once 2) Execute all loops 3) Exercise all logical decisions 4) Exercise internal data structure to ensure their validity
8) What are the 5 points of the difference between configuration testing and compatibility testing? A) Compatibility is to check or test t est how the built application adopting or compatible with different operating systems like IE,Firfox etc Configuration Configuration test or portable test is to check how well the built application is compatible with different hardwares in the company
9) How do you test if we have minimal or no documentation about the product? A1) In case we dont have any documentation about the product we can do exploratery testing. Also We can prepare the test cases according to the product,and by running those test cases, testing can be performed. A2) Testing is always performed against a given set of requirements and expectations. In the absence of these, one must first try and gather as much information and requirements on the product. This is achieved by:
- Performing Exploratory Testing (Perform a detailed study of the product / application under test, and make a list of features and functionality. The approach usually taken is a depth first breadth later approach.) - Interview the individual responsible for purchasing or procuring the product and understand his/her requirements One you are done with these, construct a details functionality vs. requirement map. This will act as Mini Functional Specifications document. This document can then server as your reference document to perform detailed structured testing activities.
10) What is difference between Defect Age & Build Interval Period? A) Defect Age : The time of introduction of defect to time of detection. To compute the measurement one assigns a number to each software development life-cycle phase and calculates difference between detection phase with introduction phase (i.e. " analysis" can be assigned a 1, "design" a 2, "coding" a 3, etc. for computation of defect age). Build interval period: this is the time taken to build newer version of the application and older version.
11) What is incremental testing? A1) Incremental testing can be done in t wo ways: 1.Top-Down Approach In this approach,the main module is connected and the stubs are used to substitute the coordinated (sub)modules and testing is done one by one in incremental manner 2.Bottom-Up Approach The low level components are connected as cluster and the test driver (which is a program code) are used to drive to main and testing is done on cluster one by one . A2) There are 2 types of Integration Testing 1) Incremental Intigration Testing 2) Non-Incremental Intigration Testing. INCREMENTAL INTIGRATION TESTING:In this type of testing we have to add the interface incrementally and check the data flows between modules. For this type of testing we should know the parent / child relationship between the modules means which module is the parent / child of which module.
But if we do not know the parent / child relationship between modules then we should go for Non-Incremental Integration Testing.. But in Non-Incremental Integration Testing it is very difficult to a) Find out the Root cause of Defects. b) Test all possible interface between the Modules. In some cases both Incremental and Non-Incremental Integration testing is required which is called as SANDWITCH Integration Testing.
12) What is base lining? A) Baselining :Process by which the quality and cost effectiveness of a service is assessed, usually in advance of a change to the service. Baselining usually includes comparison of the service before and after the C hange or analysis of trend information. The term Benchmarking is normally used if the comparison is made against other enterprises. For example :If the company has different projects.For each project there will be seperate test plans.This test plans should be accepted by peers in the organization after modifications.That modified test plans are the baseline for the testers to use in different projects.Any further modifications are done in the test plan.Present modified becomes the baseline.Because this test plan becomes the basis for running the testing project.
13) What methodologies have you used to develop test cases? A1) There are mainly 3 methods to Design a test case.. 1) Error Guessing ( May not be a Official Process ) 2) Equivalence Partitioning a) b) c) d)
If the If the If the Lastly
input is a Set of Value then take 1 valid and 2 invalid values input is a Range of Values then take 1 valid and 2 invalid values input is Boolean value then test for both True and False values Devide the whole range of input values in to some equal part and
take all valid values with 2 invalid values 3) Boundary Value Analysis A2) Error Guessing: The tester has to guess what fault might occur and to design the tests to represent them.
Equivalence Class Partitioning: In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still c overing maximum requirements. In short it is the process of taking all possible test cases and placing them into classes. One test value is picked from e ach class while testing. Boundary value analysis: It?s widely recognized that input values at the extreme ends of input domain cause more errors in system. More application errors occur at the boundaries of input domain. ?Boundary value analysis? testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain. Boundary value analysis is a next part o f Equivalence partitioning for designing test cases where test cases are selected at t he edges of the equivalence classes.
14) Please explain 3-tier architecture? A)3-tier Architecture means Application is not directly depending on the database it lies in between the front end and database and the tier present in between is called business tier 3-tiers are 1) Presentation Tier ( in which HTML, DHTML, JSP pages are developed) 2) Business Tier ( in which JAVA Code, JAVA Beans, EJB are used) 3) Database Tier ( Databases like SQL Server and ORACLE 9i are used)
15) What is the difference between SRS(System requirement specification) and BRS(Business requirement specification)? A) SRS is developed by the developer from the BRDor BRS that is given by client SRS specifies system requirments,screen shots of application,field level validation datas like datatype of fields BRS specifies the client requirements it will be in a more general terminology i.e. oriented more toward business of the client. Normally SRS is used of integration and system testing. BRS or BRD(business requirement document) is normally used for UAT(user acceptance testing where only the main functionality is tested
16) What are the goals of a performance testing of a web application? A) Performance testing is used for test the application with respect to handle the performance. The main goal behind the performance test on web application is to find out the reason why the application bit slow over access on the network. So it helps to improve the access rate over the network.
17) What is difference between Authentication and Authorization? A) Authentication-->Checking the validity.Ex:A creditcard validation by Verisign. It is called authenticating the CreditCard Authorization-->Giving some rights -Ex:I authorize mr.Rahul to sign some papers related with my bank accounts
18) what is the difference between QA,QC and testing? A) QA-we are talking about the process. QC-we are talking about the product QA is a planned set of systematic activities necessary to provide adequate confidence that requirments are properly established and products or services conform to the same. Whereas QC is the process by which the product quality is compared with the applicable standards and action is taken when nonconformance is detected
19) What is globalisation testing? A) The goal of globalization testing is to detect potential problems in application design that could inhibit globalization. It makes sure that the code can handle all international support without breaking functionality that would cause either data loss or display problems.
20) What is UAT testing.When it is to be done?
A1) UAT stands for 'User acceptance Testing'This testing is carried out with the user perspective and it is usually done before a release A2) UAT means user acceptance testing generally it done after the system testing two type of UAT testing alpha & Beta alpha means End user come in development envoirment and test the appliction Beta means we hand over ur product & end ur use & test application HIS/HER involvement
21) How do you scope, organize, and execute a test project? A) I would study the functional and business requirement documents. Get answers from BA and FA, if I have any questions. I would understand the functionality and figure out role and size of my module in terms of the whole application. This is the way I would understand the scope of the module and t hus its testing. I would get data, make sure environment is up and running, ensure other pieces/services are as needed (for my module to interact), and see that testing documents are approved (test plans, test design documents, test cases, bug templates etc). Per test cases that are reviewd and approved by concerned person(s).
22) What is meant by sparial model?and advantage and disadvantage? A) The spiral model is similar to the incremental model.The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. Advantages High amount of risk analysis Good for large and mission-critical projects. Software is produced early in the software life cycle
Disadvantages: Can be a costly model to use. Risk analysis requires highly specific expertise.
Project?s success is highly dependent on the risk analysis phase. Doesn?t work well for smaller projects.
23) Difference between Efficiency and Effectiveness? A) effiency means how accurately you perform. effectiveness means the usefulness of what you have done
24) what is the different between test log and test report? A) test report -----during test execution testengg are reporting mistaches to development team in an IEEE format that is called testreport test log------expected output is called testlog which is in the form of document.
25) Define quality for me as you understand it A) It is software that is reasonably bug-free and delivered on time and within the budget, meets the requirements and expectations and is maintainable.
26) what is meant by scalability testing? what is the tool used for this testing? A) We perform scalability testing to determine how effectively your Web site will expand to accommodate an increasing load. Scalability testing allows you to plan Web site capacity improvements as your business grows and to anticipate problems that could cost you revenue down the line. Scalability testing also reveals when your site cannot maintain good performance at higher usage levels, even with increased capacity. We can test over the Web or from our labs using these benchmarks and testing tools: * * * * * *
PC Magazine WebBench and NetBench Mercury LoadRunner RadView WebLoad Shunra Cloud Segue Software SilkPerformer Rational Suite TestStudio
27) How do you prioritize testing tasks within a project? A) # Purpose 1. product To satisfy some contractual requirement.
2. tool To further the testing process itself. 1. schedule 2. map Why distinguish the two? Change is inevitable; deal with it: external forces often dictate changes to the test plan. To be a useful tool, the test plan has to evolve to meet a changing environment. # Goals 1. Address product risks 2. Address project risks # Success/completion Criteria 1. Test until time runs out 2. Fraction of code/functions/features covered 3. Test until rate of failure falls below some threshold (failures/hour of testing). 4. Number of detected failures as fraction of estimated total failures (based on historical data). 5. Fraction of test cases passed 6. Ratio of failures reported to fixed 7. Fraction of total defects removed # What is a plan 1. Schedule (W5H2) The Who, What, Where, When, Why, How, How Much of a project. 1. Milestones Points of time in the plan at which significant things are supposed to happen; Milestones divide the project into phases. 1. Exit Criteria - what determines whether the Milestone has been
successfully passed. Must be ambiguous and binary (go/no-go). These can be in terms of: 1. Deliverables - what will be delivered at the Milestone, hence what is produce by work leading up to the milestone. 2. Dates - a milestone may simply be a date at which something must happen, such as a ship date or marketing event. Note: it is not possible to fix both deliverables and dates; one must be derived from another. For example, if there are certain products (deliverables) that must be delivered to meet the Milestone, then the Milestone is actually passed when t he deliverables are completed; any date attached to the Milestone is an estimate and subject to change. 2. Tasks - distinct activities, assigned to people, that must be performed to perform the work in a phase. 2. Map Like a roadmap or architect's drawing. This approach inventories the functions to be tested and the tests to be performed. The idea is to prioritize testing activities so that the most important things get done in the presence of schedule pressure. # Plan Contents The following are distilled from Rex Black. 1. Overview, defining test objectives 2. Bounds 1. Scope - what areas/kinds of tests will/will not be addressed 2. Definitions 3. Setting - environment in which the plan is carried out 3. Quality risks - risks associated with product features 4. Plan 1. Phases 1. entry criteria 2. exit criteria
3. stopping criteria 2. Milestones 1. deliverables (estimated, if date fixed) 2. date (estimated, if deliverables fixed) 3. exit criteria (same as phase exit criteria) 3. Tasks - what will be done in each phase 1. reviews to perform 2. tests to perform 3. other tasks (test implementation, lab preparation, etc 4. 5. 6. 7.
Test Environment/Configuration Resources Test and Failure tracking/management Project Risks and Contingencies
Not product (quality) risks. 8. Approvals 9. Change history 10. References # Phases Tests are performed by different roles, as appropriate to their expertise. Tests can be grouped into phases according to their purpose. Phases and roles often correspond: 1. Performed by developers: 1. Unit Test 2. Integration Test 2. Performed by testers: 1. Functional Test 2. System Test 3. Regression tests 3. Performed by customers: 1. Acceptance Test
4. Performed by other groups 1. Performance analysis 2. Stress tests # Entry/Exit/Stopping Criteria Does it make sense to begin System testing if Function tests fail? Can you even begin Function Testing if Integration tests fail? What happens if more tests fail t han pass? 1. Entry Criteria: specify what conditions must be true before a test phase can begin. Example: developers must deliver a fully integrated product that passes the ``smoke'' test before Functional testing can begin. 2. Exit Criteria: specify what conditions must be trure before a test phase can be considered complete. Example: System testing is complete when two weeks elapse with no ``show stopper'' failures discovered. 3. Stopping Criteria: specify conditions that indicate a test phase should be suspended. Example: Functional testing should be suspended if any tests reveal ``show stopper'' failures. It's possible for phases to overlap. We might specify entry criteria such that System testing of a function can begin as soon as Functional tests for that function pass.
28) If automating - what is your process for determining what to automate and in what order? A) Which test case to automate: 1: test cases that need to run for every built.(also called sanity testing) 2: test that uses multiple set of datavalues for same actoin(called data driven testing). 3: identical test that need to be executed using different browser. 4: mission critical pages or transaction with pages that wont change is short term. Generally speaking more repeatative the execution better the condidate for automation.
29) What is structural and behavioural Testing
A) Structural Testing: It is basically the testing of code which is called white box testing. Behavioural Testing: It is also called functional testing where the functionality of a software is being tested. This kind of t esting is called black box testing.
30) How do you know when the product is tested well enough? A) WHEN THE PRODUCT PERFORMES ITS REQUIRED FUNCTIONS IN SUCESSFULL MANNER
31) When is a good time for system testing? A) Once the intergartion testing is over and found that a minimum 80% of testcases are passed and the failed testcases are not show stoppers, then we can start performing system testing.
32) Define Verification and Validation. Explain the differences between the two. A) VERIFICATION: IS THE PROCESS OF TESTING LIKE SET OF DOCUMENTS,PLANS,SPECIFICATIONS AND REQUIREMENTS. Verification answers the question " Are we building the product right(i.e according to the requirements?); VALIDATION: iS THE ACTUAL TESTING OF AN ACTUAL P RODUCT. Validation answers the question " Are we building the right product (i.e what the customer needs?)
33) what is meant by waterfall model? What is advantage and disadvantage of waterfall model? A) In this model every phase should be implemented in a sequential manner. output of one phase should be the input for next phase.we select this model if projects is small in size and user requirements are constant . drawbacks: time consuming process. if any mistake in above phases ,same mistake will be repeated till the end of the process.This model does not allow the change of the user requirements. 34)
Give me 5 strong & weak points of yours
A) Strengths are I'm well motivated, well-organized, detail-oriented team memberI've got a strong desire to succeed, and I 'm always ready and willing to
learn new information and skills. And about my weakness, I'm always ready to learn new skills and adapt my methods to become better at what I do. If I become aware of a weakness in my knowledge base or in the way I perform my duties, I do my best to fill that gap whether through formal training, informal training, or directly from my colleagues.
35) What are basic, core, practises for a QA specialist? A) QA always monitors the project from b eginning to end. if there is process violation takes places then he takes a CAPA(corrective action and preventive action). his work is preventive work. he does his work by conducting reviews,meetings, walkthroughs usin check lists, issue lists.
36) When should you begin test planning? A) Test Planning should begin before the design phase itself.You can plan testing when you get the requirements,so that you can set the testing requirements,the schedule,aspects to test,decide on personnel and any training required etc.Actual testing can begin once the system is being built.
37) Give me some examples of how you have participated in Integration Testing. A1) After all the components are build for an application, testing the entire flow of the application end-to-end is known an Integration. E.g. in some projects there will be multiple systems which works together, so we need to integrate all systems and test it. A2) integration testing is a process by which we are going to check the communication interface between the different modules.i used to perform integration testing when i checked whether the data inserted into one from should display in the other form.this is really a kind of integration testing.
38) What is good code? A) a code which is 1.bug free 2.reusable 3.independent 4.less complexity
5.well documented 6. easy to chage is called good code
39) What did you include in a test plan? A) Title of Project Author Name,Version ..Date ofPrearation 1)Introduction 2)objective 3)Intended Audiences 4)Accronyms 5)Trest Process 6)Kinds of testing 7)Test apporch 8)Functions to be Tested 9)Functions not to be Tested 10)Pass/Fail criteria 11)suspention/Resumsuntion Criteriya 12)Test Environments 13)Test Delivarables 14)Prorities AND Severity 15)Responcibilities 16) Enty/Exit criteriya 17)Rease Notes
40) What is IEEE 829? (This standard is important for Software Test Documentation- Why?) A) IEEE 829-1998, also known as the 829 Standard for Software Test Documentation is an IEEE standard that specifies the form of a set of documents for use in eight defined stages of software testing, each stage potentially producing its own separate type of document. The standard specifies the format of these documents but does not s tipulate whether they all must be produced, nor does it include any criteria regarding adequate content for these documents. These are a matter of judgment outside the purview of the standard. The documents are: * Test Plan: a management planning document that shows:
* * * * *
How the testing will be done Who will do it What will be tested How long it will take What the test coverage will be, i.e. what quality level is required
* Test Design Specification: detailing test conditions and the expected results as well as test pass criteria. * Test Case Specification: specifying the test data for use in running the test conditions identified in the Test Design Specification * Test Procedure Specification: detailing how to run each test, including any set-up preconditions and the steps that need to be followed * Test Item Transmittal Report: reporting on when tested software components have progressed from one stage of testing to the next * Test Log: recording which tests cases were run, who ran them, in what order, and whether each test passed or failed * Test Incident Report: detailing, for any test that failed, the actual versus expected result, and other information intended to throw light on why a test has failed * Test Summary Report: A management report providing any important information uncovered by the tests accomplished, and including assessments of the quality of the testing effort, the quality of the software system under test, and statistics derived from Incident Reports. The report also records what testing was done and how long it took, in order to improve any future test planning. This final document is used to indicate whether the software system under test is fit for purpose according to whether or not it has met acceptance criteria defined by project stakeholders.
41) What made you pick testing over another career? A) Testing is one aspect which is very important in the Software Development Life Cycle (SDLC). I llike to be part of the team which is responsible for the quality of the application being delivered. Also, QA has broad oppurtunities and large scope for learning various technologies. And of course it has lot more oppurtunities than the Development.
42) What did your base your test cases? A) Functional design document and technical design documents are the basis for preparing testcases. These documents include the specifications and requirements of the client. These documents help us to get f amiliar with the client requirements. We have to start preparing the testcases after thorough with client requirements.Thorough study
helps to write all testcases without missing any client requirements, which further helps in testing all the client requirements.
43) How would you ensure 100% coverage of testing? A) We cannot perform 100% testing on any application. but the criteria to ensure test completion on a project is 1. all the test cases are executed with the certain percentage of pass. 2. bug falls below a certain level 3. test budget depleted 4. deadlines reached(project or test) 5. when all the functionalities are covered in a test cases 6. all critical & high bugs must have a status of CLOSED.
44) WHAT IS GAP ANALYSIS? A) Gap analysis is mainly done when there is an existing system or product which is going to replace a new system.The gap analysis is the functional difference between the existing functionalities and the functionalities available with the product. This will be a part of the requirement analysis phase
45) What is Cyclomatic Complexity? Explain it with example? A) Cyclo complexity is a measure of the number of linearly independent paths through a program module. It is a measure of complexity of code related to the number of ways there are to traverse to piece of code. This determines the minimum number of inputs you need to test all ways to execute the program.
46) Describe any bug you remember. A) For example in our Project, the bug was like Sales Tax should be calculated w.r.t the Address on Shipment, but in the address if some Space is given in b/w, the sales tax was not calculating. in my application there is a form called Customer Registration . the fuctionality of that form is after filling the fields we press insert button on the form. at that time the data is not stored into the table. it was missed somewhere in the middle.
Or In my module - there is a " on board life time" hh/mm minutes more than 59 - hour should be added by 1. but even if the user enter the minutes value more than 59 found this BUG and logged it in Prolite bug reporting
- in which - if the user enter in the first build i found that - hour is not increased. - SO i tool.
Or The bug I remember is , we have a project for uploading banners, every user has fixed number of banners that can be uploaded , but the problem was if the limit was exceeding the error message displayed was flashing for only few seconds and till the user will read it , it use to vanish and the screen used to go to the next page .I found this bug and reported in the bug report.
47) what is terminologe?why testing necessary fundamental test process psychology of testing? A) Testing Terminologies : Error: a human action that produces an incorrect result. Fault: a manifestation of an error in software. Failure: a deviation of the software from its expected delivery or service. Reliability: the probability that the software will not cause the failure of the system for a specified time under specified conditions.
Why Testing is Necessary Testing is necessary because software is likely to have faults in it and it is better (cheaper, quicker and more expedient) to find and remove these faults before it is put into live operation. Failures that occur during live operation are much more expensive to deal with than failures than occur during testing prior to the release of the software. Of course other consequences of a system failing during live operation include the possibility of the software supplier being sued by the customers! Testing is also necessary so we can learn about the reliability of the software (that is, how likely it is to fail within a specified time under specified conditions).
48) What is the exact difference between Integration & System testing, give me examples with your project. A) Integration testing: This test begins after two or more programs or application components have been successfully unit tested. The development team to validate the technical quality or design of the application conducts it. It is the first level of testing which formally integrates a set of programs that communicate among themselves via messages or files (a client and its server(s), a string of batch programs, or a set of on-line modules within a dialog or conversation.) System testing: During this event, the entire system is tested to verify that all functional, information, structural and quality requirements have been met. A Predetermined combination of tests is designed that, when executed successfully, satisfy management that the system meets specifications. System testing verifies the functional quality of the system in addition to all external interfaces, manual procedures, restart and recovery, and human-computer interfaces. It also verifies that interfaces between the application and the open environment work correctly, that JCL functions correctly, and that the application functions appropriately with the Database Management System, Operations Environment, and any communications system.
49) What is the V-Model Development Method and do you agree with this model? A) V-model gives the equal importance for both t esting and development. It says testing need not to be occurred once the code is delivered, instead it can start early with requirements in preparation of test criteria.
50) What is software quality assurance? A) QA is a activity which is always concentrates on improvement of process. it is a prevention activity. these people always monitoring the process, if there is process violation takes place then these poeple take coresponding corrective and preventive actions
51) At what stage of sdlc testing starts. A) We can map SDLC with Testing in the following way: In the requirements stage a tester can s tart writing a testplan. In the designing stage, a tester can start writing 60% of Testcases. In the Coding stage, a tester can write the remaining testcases aftre studing the functionality. In the testing stage, a tester can start different kinds of testing.
52) What are the common bugs encountered while testing an application manually or using test director,winrunner A) the common bugs encountered during the testing process are mismatch errors, runtime errors, exception handling errors, data less or wrong data.
53) What are the Testing levels and types A) there are two levels of testing:1 Low level testing a) Unit Testing b) Integration Testing 2 High level Testing a) System Testing b)Performance testing , Acceptance Testing Etc.
54) What is the responsibility of programmers vs QA? A) Programmers: To build the project or product according to the specification. Tester : To determine the project or product satisfy the specification requirments without any defects.
55) We believe in ad-hoc software processes for projects. Do you agree with this? Please explain your answer.
A) Ad-hoc testing should used only when the requirements are not written,or is not documented like an extereme programming .Normal projects where there are baselined requiremnts ,should not follow ad-hoc testing procedure.It must have testplan,testcase,testreport.
56) What kinds of testing have you done? A) I have done functionality testing, GUI Testing, Database testing, Regression Testing. Also involved in Smoketesing once a build is released from the development team. I have done follwing testing : i)Usablity ii)Integration testing iii)Smoke and sanity testing iv) Functional testing v) Functional testing (with automation) vi) System testing vii) Regression testing viii) Release testing (build testing) and so on
57) What is Configuration management? Tools used? A) Software configuration management (SCM) is the control, and the recording that are made to the software and documentation throughout the software development cycle (SDLC). SCM covers the tools and processes used to control, coordinate and track code, requirements, documentation, problems, change requests, designs, tools, compilers, libraries, patches and changes made to them, and to keep track of who males the changes. Tools include Rational ClearCase, Doors, PVCS, CVS and many others.
58) How do you analyze your test results? What metrics do you try to provide? A) Test results are analysed to indentify the major causes of defect and which is the phase that has introduced most of the defects.This can be achieved through cause/effect analysis or Pareto analysis.Analysis of test results can
provide several test matrics.Where matrics are m easure to quantify s/w, s/w development resources and s/w development process.Few matrics which we can provide are: Defect density: total no of defects reported during testing/size of project Test effectiveness: t/(t+uat) where t:total no of defect recorded during testing and UAT: total no of defect recorded during use acceptance testing Defect removal efficiency(DRE): (total no of defect removed / total no of defect injected)*100
59) How do you perform regression testing? A) Regression Testing is carried out both manually and automation. The automatic tools are mainly used for the Regression Testing as this is mainly focused repeatedly testing the same application for the changes the application gone through for the new functionality, after fixing the previous bugs, any new changes in the design etc. The regression testing involves executing the test cases, which we ran for finding the defects. Whenever any change takes place in the Application we should make sure, the previous functionality is still available without any break. For this reason one should do the regression testing on the application by running/executing the previously written test cases. If that pies of code modified for some reason, testing needs to be d one to ensure the changes are not negatively impacted the previously working functionality
60) What is UML and how to use it for testing? A) The Unified Modeling Language is a third-generation method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development From the inside, the Unified Modeling Language consists of three things: i) A formal metamodel ii) A graphical notation iii) A set of idioms of usage
61) what is backward compatibility testing ?
A) Oprating system is compatible to our build ,but our build is not compatible with opearating system,called backward compatibility.generally test enginers face backward comp.rather then forward comp.
62) What is meant by recovery and realization testing? A) Recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. The realization includes all the internal activities of the supplier or of the IT department before the final product can be delivered to the end-user or to the customer. Realization testing is possible in each and every phase mentioned below:(Either it may be verification or validation) programming or coding the software customizing and configuring the package or the programs writing the documentations performing the internal tests
63) If the interviewer gives you some documentation and asks you to create a test plan, what should you say do? A) First thing is you need to do is just find out what kind of documents are those. For example he is asking you to go through BRD,SRS,TRD and soo on. If you can get yourself familarize with the kind of document you are going through, then come to the conculsions what kind o f requriments are bring illustrated in the documnet. For example if you are going through a BRD (business requriment document) you can information like what exactly the business requires. If you are going through a SRS (Software requriemnts specification or System requriement speicifcation) you can a very clear picture in this document than the B RD. Since here this document speaks about the system mainly.
64) How would you define a 'bug'?
A) Bug can be defined in several ways.some of them are here. 1.Deviation from expected result to actual result. 2.Non-Confirmance to client requirement,, & 3.bug is a coding error in a computer program.
65) What is the difference between a test strategy and a test plan? A) Test Strategy: It is a Document and it specifies required test to be applied on corresponding build. Test Plan: It is a Document and it specifies "What to test", "When to test", "How to test", "Who to Test".
66) If the tester is on vacation how can we handle the situtation in his absence A) First of all the processes should be such that there is minimal dependency on a person. I would always have a back up testing resource though he may be in a different team but atleast he would have some knowledge about what the application is, where all the updated test cases are placed. Moreover, ensure that the test cases that are written are of high quality. Each step is well documented and easy to understand. Any dumb user should be capable of executing the steps from the test cases and interpret the results. This should solve the above problem. Any comments or s uggestions on my views are welcome!
67) Would you like to work in a team or alone, why? A) I would like to work in a team. Because the process of software development is like a relay race where many runners have to contribute in their respective laps. It is important because the complexity of work and degree of efforts required is beyond level of an individual .
68) What is Scenarios in term of testing A) Scenario means development. We define scenario by the following definition:Set of test cases that ensure the business process flows are tested from end to end. It may be independent tests or a series of tests that follow each other, each dependant on the output of the previous one. The term test scenario and test case are often used synonymously. A set of test cases ensure that the business flows are tested from end-to-end. The Definition of Test Scenario is: A thread of Operational use at any level of testing.
69) What is localization testing A) Localization Testing is nothing but testing the languages now a days all applications r devoloping in all languages so here we wil check the application in different languages
70) what is the main difference between Boundary value Analysis and Equivalence partitioning. A) BV analysis- we only check the boundary values and +or -of that values EP- first we divide the boundary values into some range with respect to that range we can check for example if u want to check 0-10 first divide the range- 3 1.checking for <0 2. Checking for >10 3. In between0 to 10 5
71) Define the following and explain their usefulness: Change Management, Configuration Management, Version Control, and Defect Tracking.
A) Software Configuration Management (SCM) is the control, and the recording that are made to the software and documentation throughout the software development cycle (SDLC). SCM covers the tools and processes used to control, coordinate and track code, requirements, documentation, problems, change requests, designs, tools, compilers, libraries, patches and changes made to them, and to keep track of who makes these changes. Tools include Rational Clear Case, PVCS, CVS, VSS and many others SCM - helps to track the project development and keep a track of the history and changes incorporated with date specifications. =================================================================== Version Control :- Refers to the build numbers and the features included in each version with reference to the client modifications received and accepted. Depending upon the changes accepted, these are scheduled in either the current Build version or decided to be incorporated in the next B uild release. Build version follow the international naming convention as follows :- 01-01-01 "01" The first 2 digits refer to the Build release number by the client. 01-"01"The next 2 digits refer to the internal release number to the client. Meaning before the project is announced the client's internal users check out the functionality. So any changes suggested by the clinet and accepted would be r eflected here. 01-01-"01" The last 2 digits refer to the internal version at the place of development. For e.g if an error is found in say Build 01.01.01 and is fixed in the next verison. The build will have the internal version release number as 01.01."02" Version control helps track the development process in a project along with d efect tracking. Also each release number can be associated with features incorporated and the errors foudn and closed int hat version number. Defect Tracking :- Refers to the tracking of defects with reference to the Build version in which they were found and their status. For e.g Run time error foud in Build V.1.01.02 dt :- 12 Sept 2005 Status Closed in Build V.1.01.03 dt :- 14 Sept 2005.
Major Defects that have been left open n eed to be tracked so that before deployment their status is closed. Defects are also tracked so as to form a database for analysis at the time of completing Testing Metrics like - Defect Density etc.
72) How to break an application by testing ? A) One of the charecteristic of a test engr is to break the system,basically a TE tries to break the system in various ways like functionality testing,performance testing,security testing and if the build has been developed flawless then there is no chance that you can break the system,you can break the system by going for reliability testing or any other testing of the same kind Eg.You might suddenly shut down the computer while u r using the system to see if it backs-up all the data without user intervention before u shut it down....so it also depends upon the development's efficiency.
73) How did you go about testing a project? A) As to the difference between integration testing and system testing. System testing specifically goes after behaviors and bugs that are properties of the entire system as distinct from properties attributable to components (unless, of course, the component in question is the entire system). Examples of system testing issues: resource loss bugs, throughput bugs, performance, security, recovery, transaction synchronization bugs (often misnamed "timing bugs").
74) What you mean Domain Specific Testing? Testing is not Domain Specific? A) Domin is a One specific area, Domin Testing goal is to check values taken by a variable, a condition, or an index, and to prove that they are outside the specified or valid range. It also contains checking that the program acepts only valid input. 1) Boundary value analysis 2) Equalance class. 3) Cause-Effect Graph.
75) What is Traceability Matrix ? Who prepares this document ?
A) raceability matrix/ Requirement Traceability matrix (RTM) This is a document prepared to map the requirements from the SRS with the test cases at each level of testing like unit, integration & system. It assists in kepling track which requirements has been covered.
76) For a bug with high severity can we give the priority also to be high...If so why we need both? For example severity=1 and priority=1...Cant we have only priority/severity?? A) Severity and priority of a bug need not be same. With high severity we can give low priority and vise versa. Severity means what is the impact of the bug found and priority vary based on the requirement priority release plan / development team.
77) We believe in ad-hoc software processes for projects. Do you agree with this? Please explain your answer. A) Ad-hoc testing is very much essential as From Starting means Development to Testing all have to follow the requirements so developer will develop the application as per requirement and tester will test the application as per requirement also indirectly we can say both the developer and tester are in a same and systamatic way so there may be a lesser chance to find out the defect but you think as per End-user , he will never use the application in a proper way as per his requirement we will try to use.. so to avoid this type of problem we should go for Ad-hoc Testing and second point is If we have no suffient time to test the application at that case we should go for Ad-hoc Testing also..........
78) What type of metrics would you use? A) QAM: Quality Assurance Matrix TMM: Test Management Matrix PCM: Process Compatibility Matrix
79) what are six sigma standards how many types are there A) It is a standard used to improve bussiness quality. The six sigma cycle is Define-->Measure-->Analyse-->Improve and -- >Control
80) What is version control A) Generally, in testing time development team passes builds with unique numbers to testing people. All these builds are placed in a secured folder.We can also place our Design specifications, Test cases documents, bug reports, review reports, specs and everything which are related to our project. For this we'll use a tool which is called as version control tool or configuration management system. For every person there will be an i d which is created by PM. We have to check out the documents whenever we want to make any modifications or to add any information to it. after that we'll save it and we'll check in into version control system. Our account is accessed only by ourself and PM and TL.
81) What are ISO standards? Why are they important? A) ISO 9000 refers to Quality Mgt. This means what the organization does to e nhance the customer satisfaction by meeting customer and applicable regulatory requirements and continually improve its performance in this regard. This is important as there are systems and processes in place to monitor performance across various parameters both for the employees as well as employers and this results in overall good performance for the organization. There are various levels in place which certify the organization's way of doing work and each level attained helps track an organizations good will and work performace on a common level working field on the international level.
82) Write a test case for testing a printer which should work based on LAN configuration?
A1) 1.server should give axcess to client if client give a printer command. 2.first client should get permmsison from server 3.the error message should be displayed to client if s erver denied the axcess we can write so many like this.. A2)1)check that all system and printer connected in lan 2)check that client must be access server 3)client should be get permission for access printer 4)if server denied his/her req there should be p roper message displayed 5)if server accept req there is show message for connection stablish
83) How do you go about testing a web application? A) It?s clear that for testing any application, one should be clear about the requirements and specification documents. For testing Web application, the tester should know, what the web application deals with. For Testing Web application, the test cases written should be in two different types, 1) The Test cases related to the Look and Feel of the Web pages and navigation and 2) The test cases related to the functionality of the web application. Make sure, whether the web application is connected to the Database for the inputs. Write Test cases based on the Database and write test cases for the backend testing as well if there is any database. The web application should be tested for the server response time for displaying the web pages, Make sure the web pages under load as well. For load testing, the tools are very much useful for simulating the many users.
84) What are those few areas where manual is preferred over automation testing? A) Automation is greate tool of testing over a manual testing. But still there are certain areas where it is not applicable. Mostly UI (User interface) testing we can not automate. That means if we want to check usability of software we should go f or manual testing only.
85) What is meant by reliability testing and in which phase this test is performed and by whom? A) reliablity testing in the sense recovery testing,i.e suppose u r application going to abnormal condition with the help of b ack up u r application comes to normal position
or not for example:suppose suddenly power off ,with the help of back up (ups)u r system coming to normal position
86) what is release candidate??? A) Relase candidate is a pre-release version. Which contains the desired functionality of the final released version,which needs to be tested for bugs.(which idealy should be removed before the final vesrion is relased)
87) What is the Test we are going to do when a New Build is come to test environment(i mean whether it is smoke or sanity and next stage what is ? please give with example? A) Generic Sequence 1. Run Smoke Test Plan 2. Execute Functional Test Plan ( If planned ) 3. Verify Bug Fixes 4. Execute Regression Test Plan ( applicable to builld under test, if planned ) 5. Based on above executions decide ( probably test lead/QA manager ) whether this build can be accepted Assuption: Question says "New Build" so my assumption was, there were prior builds to this. Only in this scenario the above sequence is valid. If you meant "First Build" secnario varies
89) How will you test notepad? A) For notepad we could check the following things 1. Creating a file(functionality & usability) 2. opening a file(functionality & usability)
