1.How you will test media player ?We can test media player with the following aspects,1)Playing different file formats (AVI, MPEG, DIVX, MP3, RM, MID, WAV)2)With and without installing codecs3)With different display resolutions4)High and low DPI settings5)Streaming video6)Whether AUDIO and video from movie file are synchronized or not
7)Then functions like Play, Pause/resume, stop, Play list
2.what are the stages in Testing life cycle?The stages in Testing life cycle are:1.Test Requirement 2.Test Planning 3.Test Environment setup 4.Test case design or contruction 5.Test Execution 6.Defect tracking 7.Regression Testing 8.Test Report
9.Test Closure
3.what is unit testing? It comes under white box or Black Box testing?Unit testing is Module wise testing of Application. As Unit testing is done by Programmer this testing is done for code testing i.e. White box testing. On the other side Manual testers do manual testig for it i.e. Black Box testing
4.Difference between QA and Testing?QA is responsible 4 monitoring and improoving entire S.D.L.C phasess nothing but preventing the bug testing is finding bugQA: Prevention of errorsTesting: detection of errors.In detailQA is the process to ensure that all the procedures and standereds are establish and followed throughout the life cycle.Testing is the process to execute the system in both Favorable and unfavorable conditions in order to find the bugs.In favorable conditions it produced the correct results and in unavorable conditions it produced the correct results.
5.what is the difference between Load, Stress and Volume Testing?Load: It is opposite of Stress testing.Oprate the software with largest data files.Connect as many as users to the application and told them to login at the same time.how the application reacts under heavy loads(done using virtual users).Stress: how the application reacts under low memory, low disk spaces, slow cpu speed,Slow modems.We have to find the minimum condition upto which it can work
Volume: how the application reacts for growing database.
Find problems with max. amounts of data. System performance or usability often degrades when large amounts of data must be searched, ordered etc.The system is run with maximum amounts of data. Internal tables, databases, files, disks etc. are loaded with a maximum of
data.Maximal length of external input.Important functions where data volume may lead to trouble.
6.what is penetration testing?Penetration testing is nothing but security testing i.e how well the application provides security against unauthorized internal or external access 7.What is smoke testing?The exercise to carry out to check the Application Build is working fine and stable for the Extensive Testing @ the Tester's End. Basically the testing is done by the Developers before the Build delivered to QA team.1. Checking for the basic functinality or basic features of the projectonce we receive the build is called Smoke Testing.2. If any of the basic functionality is failed, then we dont continue with testing. we simply reject the build. It means we will check whether the build is stable or not.3. Here we will select some of the functionality test cases and these test cases are called smoke test cases. All these
test cases should be passed.
8.What is pairwise testing?All-pairs testing or pairwise testing is a combinatorial testing method that, for each pair of input parameters to a system tests all possible discrete combinations of those parameters.
9.What is Concurrency Testing?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
10.what is volume Testing?testing the software with heavy volumes of data. it is done
to findout memory leaks and buffer overflows.Testing that purposely subjects a system (both hardware and software) to a series of tests where the volume of data being processed is the subject of the test.Such systems can be transactions processing systems capturing real time sales or could be database updates/deletes and or data retrieval or you can say that It is to test the volume of data is acceptable to meet the projected capacity of the organisation's business processing.
11.What is Data Flow Testing?This comes under White Box Testing. Data-flow testing looks at the lifecycle of a particular piece of data (i.e. a variable) in an application. By looking for patterns of data usage, risky areas of code can be found and more test cases can be applied.
12.What is Driver and Stub?
Stubs: dummy modules used for testing if higher level modules are working properly.
Driver: dummy modules used for issuing calls to lower modules and testing if the lower modules are working properly.Stub is a part of Intgeration TestingIntergration Testing 1>Top down-Use stubs to test the module.Stub is a dummy module replaced in order to test the main module so that we are sure that the integration between both the modules works fine 2>Bottom Up-- Use driver to test the modulethe test data is sent to main module thru the drivers(also called Test Harness) 13.what is Regression testing? when it will be needed?re execution of test cases on the modified build to determine whether the defects are closed or not.The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no otherpreviouslyworking functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the Software 14.what is parallel testing?Comparing our Product / Application build with other products existing in the market.Parallel Testing is also known as Comparative Testing / Competetive Testing. 15.What is stub and driver in integration testing ? Explain with example.types of integeration testing:top downbottom upTop down : testing hierarchy starts from higher level to lower level.if suppose testers dnt get the lower modules for testing(consider the lower modules are under developmnt)wat the testers wil do thy wil place dummy modules and integerate these dummy modules with the higher level modules.in top down apparoach the dummy modules r called Stubs.Stubs- Def stubs r the dummy modules tht simulates the low level modules.Bottom up: in this the dummy modules r called drivers.Drivers- Def: drivers r the dummy modules tht simulate the high level modules. 16.what is Regresstion testing? when it will be needed?1.Regression testing is nothing but executing the same testcases on the different build. It will be needed when an bug was fixed or when a newFunctionality is added to existing functionality..2.Re execution of test cases on the modified build to determine whether the defects are closed or not3.The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software 17.endurance testing?Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.it is also called soak testing. it is testing the application under heavy volumes of data for a prolonged period of time
18.Branch testing comes under white box testing or black box testing?
White box
Branch testing is done while doing white box testing. where in focus is given on code.There are many other white box technique.Like Loop testing
19.what is the meaning of compatibility testing in view of web application testing?Checking the application on different platforms (Operating System) with different browsers,the main aim of compatibility testing is to test weather application can run successfully on different OS.
20.where testing exactly starts in v-model?testing starts from initial phase that is from requirement phase but here only static testing and continues upto codingafter that dynamic testing that is validation comes
Testing is maily two type1.static testing2.dyamic testingStating starts from requirment gathering stage.it is in the form of inspection ,reviews,walk throws,pear reviews, ect.dynamic testing starts from unit testing stage.it is actual
testing.
21.Do u writing a separate testcase for Regression Testing? If it is Yes, Explain How to write the Testcase?we r not going to write new test cases. We will select the some of the test cases from test case document, and execute the test cases to check for the bug fixes. Here we selecting the test cases such way that, all the basic functionality test cases, and affected bug test
cases.
22.What is White Box testing and who is responsible for white box testing?Testing the application with the knowledge of the internalstructure ..it comes under white box testing..In GeneralDevelopers are responsible for white box testing.
23.What is Black Box testing and who is responsible for Black box testing?Without knowing the internal knowledge of the applicatin ifyour r doing testing it comes under Black Box testing..Testers are responsible for this.Black box testing is the testing the functionality of the application and the one who is creative in thinking in different prospectives can test the application 24.What is software development Life Cycle (SDLC)? where exactly the Testing activity begin in SDLC?It is the steps followed to develop the application or software.Steps are 1. Requirement Analysis 2. Design 3. coding 4.Testing 5.Implementation 6.MaintananceTesting activity starts from the initial stade ie. From requirement analysis 25.What is the smoke testing and sanity testing..?what is the difference?In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide. A Sanity test is used to determine a small section of the application is still working after a minor change.Smoke testing is normal health check up to a build of an application before taking it to testing in depth.sanity testing is to verify whether requirements are met or not. 26.In development costs what percent Software testing accounts?if we consider 1005 as project cost64% goes to devolpement36% goes to testing 27.How do you carry usability testing?Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. 28.what are the major observations that you made when you are doing compatibility testing particularly in web applications?usually main observations are 1.what all browsers are compatible.2.what all versions are compatible.3.GUI plays vital importnat.
4.Performance also.
29.what criteria did you use to select web transactions for load testing ?You can specify different database transactions or page navigation as transaction. e.g. Login function, retrieving employee information, accessing Help page, Logout function can be treated as different transaction. It depends on your need. Normally the functionality for which you want to measure the response time is specified as transaction.
30.When should u feel that u can stop testing now?The following are few of the common Test Stop criteria: - All the high priority bugs are fixed.- The rate at which bugs are found is too small.- The testing budget is exhausted.- The project duration is completed.- The risk in the project is under acceptable limit. Practically, the decision of stopping testing is based on the level of the risk acceptable to the management. As testing is a never ending process, we can never assume that 100 % testing has been done, we can only minimize the risk of shipping the product to client with testing done.
31.How do u go abt when ur testing web applications?The quality of a website must be evident from the Onset. Any difficulty whether in response time, accuracy of information, or ease of use-will compel the user to click to a competitor's site. Such problems translate into lost of users, lost sales, and poor company image.To overcome these types of problems, use the following techniques:1. Functionality Testing2. Usability Testing3. Navigation Testing4. Forms Testing5. Page Content Testing6. Configuration and Compatibility Testing7. Reliability and Availability Testing8. Performance Testing9. Load Testing10. Stress Testing
11. Security Testing
32.How do u perform regression testing?Whenver there is a modification in existing functionality,it has to be tested again which is called regression Testing.for regression Testing we use 2 documents:Design Document
Traceability metrics
33.What is the difference between debugging and manual testing?debugging means. running the program finding errors and fixing themtesting means, running the program, finding errors and reporting the bugs
34.what is monkey testing?Testing a Software without any Testcase or formal Procedure.Navigating through various screens and checking for the functionality with some dummy/unformatted inputs and
finding bugs.it is a type of testing performed by tester.due to lack of time tester follows this type of testing. In this type he test the main functionlity of the application first and
leaves the rest.
35.what are the documents that will be created in testing cycle?while going for testing, we need the following documents. 1. SRS2. Functional Spec3. Test Plan
4. Test Case
36.what is debugging and whitebox testing and what is the diff?Debugging and whitebox testing goes hand in hand and typically done by thedevelopers.Debugging is done to verify that the program runs smoothly and running program shouldn't cause any unwanted response by the machine.whitebox testing is nothing but running the program and verify the actual behavior/result of the functionality with
expected result as predetermined.Debugging process: To find a solution to a defect cause.White Box Testing : To find a defect by executing a program or companent at the souce code.
37.What is mean by testing Methodology?testing methodology determine how to testing to be conduct starting to ending and whether testing follows standards are not, and it verify functionality.
38.what is system testing?after integration testing has been finished we will do this system testing by testing for whole system
39.what is Software testing?Software Testing is the tool to acheive the quality of the product/software...And it is checking the application againest the standards in normal and abnormal conditions...Also its main aim is towards DETECTIONwhere as Quality Assurance is defining the standards across the company and making sure that those standards are met in enterprise level.And its main aim is towards PREVENTION
40.what is the Difference between Integration testing and system testing?Integration: The process of combining components into larger assemblies.System Testing: The process of testing an integrated system to verify that it meets specified requirements.Integration Testing:Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems. System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.
41.what are the Levels of testing?1. Unit Testing2. Integration Testing3. System Testing4. User Acceptance Testing5. Operability Testing
6. Regression Testing
level 0 :: Sanity Testing test whether build is testable or notlevel 1 :: Unit testing, Integraion Testing, System Testinglevel 2 :: Regression Testing
level 3 :: Final Regression testing or Postmartom Testing
42.Does automation replace manual testing?No, Manual is the best way to test a application,. We need to automate only while regression or testing typical web applications.
43.what testing activity you may want to automate?1) Regression Tests2) Data-Driven Tests3) Performance Tests
Automation of above tests pays back effectively.
44.When should testing start in a project?That depends upon the sort of testing.there are two kinds of testing. coventional and unconventional.unconventional testing is done by the quality assurance engineers right from the initial stage of software develoment life cycle.conventional testing is done by the test engineers when they get the build from the development section.
45.What are the testing types? Tell me abt few?TYPES OF TESTING: 1.STATIC TESTING 2.DYNAMIC TESTING 3.BLACK BOX TESTING 4.WHITE BOX TESTING 5.GRAY BOX TESTING 6.UNIT TESTING 7.INTEGRATION TESTING 8.SYSTEM TESTING 9.PERFORMANCE TESTING10.STRESS TESTING11.LOAD TESTING12.FUNCTIONAL TESTING13.SMOKE TESTING14.MONKEY TESTING15.COMPATIBILITY TESTING16.REGRESSION TESTING17.USER ACCEPTANCE TESTING18.END TO END TESTING19.INSTALL/UNINSTALL TESTING20.RECOVERY TESTING21.SECURITY TESTING22.EXPLORATORY TESTING23.AD-HOC TESTING24.COMPARISON TESTING25.ALPHA TESTING 26.BETA TESTING27.MUTATION TESTING28.CROSS BROWSER TESTING29.CONCURRENT TESTING30.NEGATIVE TESTING
31.POSITIVE TESTING
46.What is alpha testing and beta testing?Alpha testing is the software prototype stage when the software is first able to run. It will not have all the intended functionality, but it will have core functions and will be able to accept inputs and generate outputs. An alpha test usually takes place in the developer's offices on a separate system.The software has reached "beta" stage when it is operating with most of its functionality, and is ready for user feedback.Beta tests enable the software to be tested in customer environments, giving users the opportunity to exercise the software, find errors, and correct them before a product is released. For beta test, the software is delivered to customers' sites, along with instructions on what features to exercise in the software. The developer records, tracks,
and addresses reported bugs.alpha testing is nothing but testing of application by user at developer site,under the monitoring of developer.beta testing is nothing but testing of application by user at user site, without monitoring of developer.
47.what is Negative testing and what It?s Purpose?negative testing is nothing but testing the application with invalid inputs and unespected conditions
48.What is the Difference between Volume Testing and Load,Stress tests..?Load, Stress and Volume testing are the part of Performence testing.Load Testing: Load Testing gauges how efficently the application performs when its functions are tested with varying workloads. Stress Testing:Stress Testing looks to see how well the software reacts and compensates when resources are low. Volume Testing:Volume Testing tests the functional limits of the application by increasing the amount of data thrown at it untill it can no longer cope with the flow.
49.What is service pack..what is the purpose of this..?This question was asked in an testing interview..that's why i posted this in this category..
Service pack may contain updates for system reliability.
50.Does functional testing comes under Black box or white box testing?functional testing comes under black box testing as the tester need not know the internal code and logic of the application. But functionality can be tested by the coder also by executing their fuctional modules and suppliying the data. hence it proves that functionality can be tested in both ways.
51.How do you do Data Base Testing?In DB testing we need to check for, 1. The field size validation 2. Check constraints. 3. Indexes are done or not (for performance related issues) 4. Stored procedures 5. The field size defined in the application is matching
with that in the db ( Database).
we can do database testing on both frent end and backend testing.in frent end we insert the values and check whether the the values are stored in dateabase on update/delete the same values in backend we can insert with insert command and check with using ddl,dml commands.
52.what you consider in security testing particularly in web applications?Security is a primary concern when communicating and conducting business- especially sensitive and business- critical transactions - over the internet. The user wants assurance that personal and financial information is secure. Finding the vulnerabilities in an application that would grant an unauthorized user access to the system is important.In security testing you must and should conduct session Tracking in very importent.Exclamation privelege, cookies poisioning, cross-site scripting, sql injection, sproofing password, access denial, authorization, etc are included in security test on web application 53.What is the difference between Testing Methodology and Testing Technics? Testing methodology is a general document or procedure followed by an organistaion for the testing department.Example object oriented methodology,Structural methodology etc.They will specify the general testing techniques for projects.This mentodologies might be talored from spiral or waterfall methodologiesTesting technique are applicable for a single project.It will change from project to project.This testing techniques can describe in test plan.It will mention what types ot testing ,needs to be done like sanity testing,smoking testing,regression testing etc. 54.What kinds of testing have you done?Black Box & White box testing are two approaches of testingMost commonly every tester perform1.Functional testing2.Regression testing3.Re-testing4.Sanity testing5.Compatibility testing6.UI testing7.Exploratory tesing (this is depending upon the type of project)8.end to end testing9.adhoc testing10.Installation testing 55.Black Box testing attempts to find errors in which of the follwing categories 1)Incorrect or missing functions 2) Interface errors 3)Performence errors?I too agree with 3 and 4 answers.Here I am giving you some information on functioanl testing,may be you people aware of this. The main intention behind functional testing is to find, is there any mismatch between your application behavior with respect to customer requirements and also we can figure out any functionality is missiing during this testing.So that,here we can satisfy the first option i.e Incorrect or missing functions. We can also find the User interface errors,which we can find out by seeying the interface and this would be also possible in functional testing. we can find the Performence errors during performance testing only,which is one type of techniques in Blockbox Testing. 56.How to conduct Regression Testing Manually?verifing the build one or more times by manually. 57.What is ur goal when ur doing Performence Testing of an Web Application..?In general there are two types of scenario's.1)Manual scenario -used in general scenario's In MANUAL SCENARIO we define the number of vusers,the load generator machines,and percentage of vusers to be assigned to each script.2) GOAL ORIENTED SCENARIO -used in the web applications in goal oriented scenario,we define the goal that our test has to achive 58.We have a testing assignment should be test in very short span.Do you think automated tests are the best solution for this type of scenario?No. Automated testing should be used when 1. there is need of regression testing.2. It needs time to write scripts. Scripts can be written ahede of time if there is time. 59.Suppose " You are given a build with 5 modules to test as per the Customer request after finalization of SRS, But the SRS contains only documentation about 4 modules. On what basis you will continue the testing of 5th module." ?if srs is available prepare test cases and to conduct formal testing if SRS is not available in this time we conduct adhoc testing.SRS is prepared based on requirements. Even SRS is not there and have requirements, we analyze the requirements first, Take the inputs from domain experts,end users. Consolidate and prepare the SRS on our own and will send the same for customer approval. based on feed back we can go with testing. 60.why we perform stress-testing,resolution-testing and cross- browser testing?Stress Testing -- We need to check the performance of the application. Def: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirementsResolution Testing-- Some times developer created only for 1024 resolution, the same page displayed a horzontal scroll bar in 800 x 600 resolution. No body can like the horizandal scroll appears in the screen. That is reason to test the Resolution testing.Cross-browser Testing This testing some times called compatibility testing. When we develope the pages in IE compatibile, the same page is not working in Fairfox or Netscape properly, because most of the scripts are not supporting to other than IE. So that we need to test the cross-browser Testing 61.What is difference between Smoke&Sanitary Testing?Sanity Test:Every time when a new build comes to the testing team then firstly sanity testing is done.Sanity consists of testing the basic functionalities of the application.Now if any major issue is reported then the build is rejected and sanity fails.Now in the next build the testing is done on the reported issue and other features are smoked out.This is smoke testing. 62.what type of testing is carried out to find memory- leakages?give me a sample example.The concept of memory leakage is related to allocation of dynamic memory in the code. Whenever the dynamic memory is used in the code for ex. in a function and the memory is not released, one is going to get the error message say "memory not available" if the function is called again and again. Though the code is syntactically and logically correct, one is going to receive the error message if the dynamic memory is used (using new command in 'C' Programming language, we can allocate dynamic memory) but not released.Certain Tools like Bounce Checker can be used to check the memory leakages. 63.Describe Software Testing life cycle? What are the steps in volved in STLC (Software Testing Life Cycle)?Software TestLife Cycle shows a structure 1. system study 2. scope\approach\estimation 3. Test Plan Design 4. Test Case Design 5. Test Case Review 6. Test Case Execution 7. Defect Reporting 8. Gap Analysis 9. Summary Report64.What is genetic testing?GEnetic testing is Analyzing an individual's genetic material to determine predisposition to a particular health condition or to confirm a diagnosis of genetic disease. 65.Adhoc testing is advisable for every project?Adhoc testing has advantage as well as disadvantage for every projectAdavantage: we check the application randomly so we reduce time consumingDisadavantage: we will check the application randomly so we miss some activities. so there is chance of bugs i that activity 66.Due to shutdown failure, one application is not running then what type of testing do u perform? Load testing or stress testing or recovery testing ?Recovery Testing 67.find the odd man out in below testing techniques. a.loadtesting b.stress testing c.recovery testing d.integration testing also tell me why?d.Integration testing.. because all other testing can performed once system/application is table and whole devlopment work over. But Integration testing we can do even if devlopment is in progress using stub or driver. 68.give examples of incremental testing?it is a continuous testing adding one by one functionality to test.Top Down approachBottom up approach 69.what is compliance testing?Complaince testing is nothing but testing whether our company follwing compleate standards r not . 70.what is the diff between smoke testing & monkey testing?Smoke testing is done to ascertain that most crucial funcctins of program work without bothering finer details.Monkey testing: done with no specific test in mind and is done randomlyMonkey testing is executing testcases radomly to check the overall functionality of the application is working or not.where as smoke testing is testing whether the application is ready for major testing or not 71.What is Cycle Testing? Not Testing Life Cycle?regression testing is the cycle testing 72.what type of documents can u prepare during Testing?Here I ma giving all the documents,which are using in our project and the authorized person,who is preparing them.It from company to company.Project Plan:Prepared by PM.QA-Project Plan:Prepared by QA ManagerTest Reports:Generally prepared by Team lead for every release.Software Metrics:Team LeadModule based Test Plan:Testing engineerTest Results:Test EngineerTestcase document:Test EngineerDefect Matrix:Prepared by Team LeadTraceability Matrix:Team Lead or team memberBu Reports: Prepared by test engineer 73.What is Test Scripts What is static testing and dyanmic testing. Explain with an exampleTest Scripts: is used to test a particular functionality (business rule). It may consist of 1 or more Test Cases. static testing: Testing of an object without execution on acomputer. (eg. review document,inspection,walk thro')simply said static means verification. dynamic testing: The process of evaluating a system orcomponent based upon its behaviour during execution(eg. functional testing,regression testing, UAT etc.,)means validation 74.What is protocol testing. whether u have used any tool in telecom testing.protocol testing is testing the performance and evaluate it in working conditionsfor wireless i have tried GlomoSim simulator, as it hasability to test 100 nodes on single cpu and for thousands ofnodes multiprocessor and parallel version is reqd. 75.Testing of Non-Functional requirements does not involove a) Performance tests b) Reliability tests c) usability tests d) Configuration testsReliability , Usability and Configuration comes under Functional requirements, and Performance comes under non functional requirements.. 76.how can u do web testing?exactly what is the process for web testing?There is no single answer for this question.If we have all the project files then we need to setup the site, by using Virtual Directories and all, there u can a link like http://localhost/VirtualDirectoryName/PageNames.Here we can also configure all DB details and all.Another way is, the dev guys directly give the URL and DB details, we need to work on the link and the specified DB details. Here the URL is like http://203.12.210.125/VirtualDirectoryName/PageNames.here 203.12.210.125 is the external IP. Another way is, when the site is in live, here the URL is like www.mytestingsite.com. Here we r directly testing the application that went to live. 77.what is meant by Adapt testing?acquiring new teststartegy/plan/TCs.. if the situation demands change 78.what r the different types of testing environments?1>Establishing a Testing Policy2>Building a software testing strategy3>Establishing a software testing method incorporating testing strategy & testing tactics4>Include test plans, test criteria, testing techniques and testing tools used in the V&V of SDLC as part of the Testing tactics 79.what is operations testing? is it coming under white box testing/unit testing?yes it comes under black box testing. we will do it in sanity testing and compatibility testing not in white box...its very important that u should devide all the desting in to different categories so that u can easily understand which testing is black box and which one is white box soon 80.What type testings will be conducted at system testing?Who will conduct each test.System testing is a type of Black box testing. System testing means testing the application. After the integration testing, usually will do system testing. Functionality, Regression, and performance testings comes under system testing. 81.As a tester what type of document req. on tester's banch to design the test cases and for executon.what will be the practical approch If we are using excel-sheet.through excel- sheet how tester communicat with developrs about the test cases and resut and what will be the cycle of testing betwen tester and developers.what type of MANGEMNT TOOL (like VSS) should be used (PLEASE IN DETAIL)by tester if he is workink in small company.As a tester we can have SRS, Usecases or any requirement where the functionality is clearly explained.Testcases are written in the spreadsheet where there should columns like Expected Results, Actual Results are updated as and when the testcase is executed and a ststus column which speaks about Pass or Fail (this should be for each step), there and we can share these spreadsheet with developers or any person(s) located on onsite, we need to have one common repository (like Lotus Notes, Bugzilla, etc.,) which can be accessed by both of them. We can maintain spread sheet for Defect Log also and the process is we need to update regularly with out any ambiguity. Coming Testing Cycle. 82.How you will choose test cases for Sanity testing and at which phase of testing you will do this.Test cases which represents the main functionality of the application. it is done at every phase till the application get exit. it is always done to check whether the application can withstand the regression testing. 83.What is Buddy testing?due to lack of time , testers and developers are group asbuddies .every buddey consist of tester and developers to continue process prallely 84.What is Mutation Testing?A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations. ---------------------------------------------Mutation Testing is a fault-based testing techniqueMeasure the effectiveness of test casesAssumption: a program will be well tested if all simple faults are detected and removedSimple faults are introduced into the program by creating a set of faulty version, called MUTANTSIn the Mutation testing we create a copy of the originalprogram that is called as mutant,and we do some changes inthe mutant program and run it with the test cases.After going through the test cases if the change is being detectby the test sace then it is called as a 'Killed Mutant' andif the change did not detect by the test cases then it iscalled as 'Equivalent Mutant'. This process is expensive. 85.What are the points to be taken into consideration while doing desktop testing?Points to be considered while performing desktop testing. 1) The icons on the screen2) task bar and its options3) start menu4) time5) items that can be launched from the task bar6) some applications have the option to be displayed as an icon on the task bar like 'Sound Control'. If udisable that option, the sound control icon must not be displayed on the task bar and the applications of the same kind.7)arrangement of icons8) background and screen saver9) Change of icon when the user changes the icon10) display of shortcuts there are many more like screen saver 86.What r the different testing techniques other than BVA and EQP?Functionality Testing, Usability Testing, Navigation Testing, Forms Testing, Page Content Testing, Configuration and Compatibility Testing, Reliability and Availability Testing, Performance Testing,Load Testing,Stress Testing, Security Testing. 87.What r the different FUNCTIONAL testing techniques?Functionality coverageinput domain testingError handling testingrecovery testingInstallation testingCompatability 88.what is scalability testing?Scalability is nothing but maximum no of users that the system can handle 89.what is Globalization testing?Globalization testing is nothing but to test all the activities based on the Standareds like ISO, SEI-CMM, CMMI and Six Segma. 90.Suppose one project is given to u.How do u know whether this project is suitable for manual testing or automation.In that project if there are no versions are maximum and there is need for more regression testing we go 4 automation 91.what type of documents do u prepare during testingdaily defect reportsweekly status reports, Monthly iwse reports Individual defect reportstest logtest planTest strategytest Methodologytest cases 92.what is exact difference between UI Testing and usability testing?In general testing team's test execution process startswith usability testing.During this the testing team concentrate on userfriendliness of application build.This usability testing is classified tnto two sub tests.1.user interface (ui)testing2.manual support testing.ui testing is used to validate every screen in terms of ease of use(understandability of screen),look and feel(attractiveness o0f screen) and speed in interface(less no.of events to complete a task ie.,short navigation) 93.What is the diff between IE and netscape in a web testing on a login page.Netscape doesnt recognise ENTER key.Net scape does not support HTML code.IE Can Support 94.What is difference between localization testing and internalization testing.Explain with an exampleInternationalization, or localization, testing involves verifying that formats and structures that vary by locale are followed.We can test for any localization inconsistencies. We will follow the standards and formatsdefined by the client, which often conform to a widely recognized regional standard such as metric vs. standard, date formats, number grouping/decimal formats, and time zone/format differences. The goal of internationalization testing is to confirm that the locale-specific formats andstandards are followed. 95.What r the inputs in System Testing?The inputs for system testing are 1. Integration testplan2. Integration test case templete (entry and exit criteria followed for each stage of testing)3.Requirement documents4.FRS(functional requirement documents) System testing is the process of testing the AUT to determine whether the application is satisfying the user requirements.it includes the following activities:Usability testingFunctionality testingLoad testingStress testingSecurity testing etc. 96.What is the difference between Project Based Testing and Product Based Testing?PROJECT BASED TESTING : TESTING CONDUCTED BASED ON THE CLIENT BASED REQUIREMENTS ONLY,SCOPE OF ENHANCEMENT IS LIMITED,BROWSER OR PLATFORM COMPATABILITY TESTING IS LIMITED TO CERTAIN EXTENT PRODUCT BASED TESTING: TESTING CONDUCTED BASED ON THE COMPANY BASED REQUIREMENTS MORE OVER COMPARING THE PRODUCT THAT RESEMBLES IN THE CURRENT MARKET TO THE PRODUCT WHAT COMPANY DEVELOPING.BROWSER OR PLATFORM COMPATABILITY TESTING TO BE DONE MORE (IN ALL BROWSERS AND OS PLATFORMS) 97.What type of Testing u done ur project?There are a few diff's on kinds of testing.but broadly we say that either the appln is web based...or stand alone... u can say u have donesmoke Testingsanityexploratorymutationnaigationsecuritybrowser compatabilitylocaliazation...rarely usedetc.... 98.What is the difference between User Acceptance Testinga and System Testing?User acceptance Testing is performed by the Client of the applcation to determine whether the application is Developed as per the requirements specified by him/her.it is performed within the development of the organization or at the client site.Alpha testing and Beta testing are the examples of Acceptance Testing.System testing is perfomed by the Testers to determine whether the application is satisfyiing the requirements as specified in SRS. 99.What is the Differnce between Client/Server Testing and Web Based Testing?In Client base application you can crate a shortcut icon for open direct application without using a server path and also use the maping to access the server .But in web based application you use the link like yhaoo.com to connect the server. 100.what is agile testing?agile testing is used whenever customer requirements arechanging dynamically 101.What is Recovery Testing?Recovery Testing is the testing which is used to find how well the application will get recover from crashes.Evaluates the contigency features are built in the application for handling interruptions and to return to specific check points. This test also assures that disaster recovery if possible. 102.what is exploratory Testing?When a tester test a application by exploring with his prevoius experience and based on the application tetser writes testcases.Thisn is exploratory testingSuppose we dint having any testing docuemts that r related to our aplication...and also we dont know the functionality of the application ...then this time we go for exploratory testing...in this type of testing we know the functionalyt of the application.. 103.What is Comparision Testing?We can use this testing to find different between two consegative application versions or two similar type of applications.. 104.Which level is costlier to identify a bug? Either in Coding Phase or Testing Phase.. Explain in Detail?Indentifying a bug is costlier in Implimentation phase. Once the software is out and used by the users it becomes very expensive to fix major bug. It is cheaper to fix bug in the initial phase of SDLC, which is requirement phase. 105.When to Stop Testing?1. When there is no time and budget2. When maximum number of test cases are executed3. All the Requirements are mapped that is RTM is filled completely4. When Test coverage is > 80%5. when bug rate falls below certain level106.What components will be covered in the web site testing?
In web testing we need to define the scope of the testing,Web testing has performance testing and functionality testing. In functionality testing we will test the look and feel of an web site and validation and see that all the links have any url associated with it, and test for the user
friendliness, more importance is given to see that user interface is proper.in performance testing we should see the how much load does thie web site can handle and do stress testing and see that all the pages comes according to universal stands. 107.what is the entry & exit criteria of testing process?Entry Criteria:1 All code of application, unit tested.2 Test plan, test cases revieved and approved.3 QA/Tester get significant knowledge of application.4 Test environment/test ware get prepared.5 After getting application build. Exit Criteria:Deadlines (release deadlines, testing deadlines, etc.) Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends 108.what is 4 p's? Exact difference between testing and QAThe 4 P's of Interviewing---1. Preparation. 2. Practice.3. Personal presentation.4. Pertinent questions. Difference B/W Testing and QA--1)Testing consider the testing of the application, whereas QA ie Quality Assurance is contain both Testing and the Programming process.2) Tester has the authority of one or some module only for the testing ie only to find out the bugs . whereas in QA ,QA has the responsibility put his/her control from starting to end.3)Testing comes after the Coding Stage. whereas QA works from the project start to project end. 109.What is red box testing and yellow box testing?Acceptance testing, often referred to as Red-Box testing 110.In an Testing interview the following question asked. who will write usecases?The use case prepared by test lead or senior test engineer 111.what is thee diff between functionality testing and blockbox testing?Functional Testing is the major part of Black box testing in which the functionality of the AUT should be tested. Where as Black Box Testing means testing the application based on its performance with out concerning its internal design. 112.what r testing tools ,bug tracking tools, test management tools & configuration tools used in ur company?Testing tools: Winrunner,QTP & Rational robot(silk test)Bug tracking tools: Bugzilla & Bugtracker Test management tool: Test director
configuration tool: VSS (Virtual Source Safe)
114.who will prepare Functional requirements specification(FRS)
It will be prepared in the Client End
115.One simple question I had faced in one of the interview.But I was unable to give the proper answer for it. Question is "Tester will raise the defect.Then y the defect have to be send to the corresponding TL of the team for conformation?Y The tester is not confident withthe defect? If yes then how did he raise the defect?" Plz read it clearfully and answer it with app. answer.1.Tester once finds any defect generally confirms it for himself by retesting it again. Once he is confirmed that a defect exists, he has to find out if its a duplicate as a tester will generally not have an idea whether the defect that he has found is not a duplicate one. and also a TL will have clear idea as to whether the perticular defect needs what sort of action. i.e state of the defect [open,reopen,assign, deffer, or any other state ]. so it is safe to consult the TL for verify and validate the defect.2.After finding the defects, Tester logs the defect which is open status. QA Lead will review the defect and assign the defect to devolopers who works on the particular component which is assigned status and change the severity of the defect if there is a real need.
116.what is testing techniques,testing methodology,test packs,how are they differentiated?Testing Technique is the procedure you undertake to test agiven software for example black box and white box testing.Testing methodologies are the ways in which you test asoftware such as unit testing,integration testing.Test Packs are the complete set of test cases and testscenarios for testing a given software.
117.In the Testing, How do we find the Duplicate Defects. In the case of testing is going on On-site r off-shore..some times on site and off-shore people may enter defects at the same time..those may include duplicate defects. how we have to find those defects.If we are using some defect reporting tool then this defectsare available on online for both offshore and on site people.As a normal practice before going to enter a bug our testing people will check the bug already entered in to the defect reporting tool or not.If the bug mistakenly entered again the development people (Project Manager)will make it's status as duplicate bug.If we are not using and defect reporting/defect management tools then it is very offenly the people enter dulplicatebugs.
Tracking also very difficult,and nearly impossible.
118.What is the diff bet Message box and Dialog box,anybody can answer it.... Thanks in advanceMessage BOX************An alert box, sometimes called a message box, is a smallwindow that pops up on your screen to warn you that yourcomputer is about to perform an operation with potentiallydamaging consequences. For example, when you choose to emptythe Trash or Recycle Bin on your computer, an alert box maypop up, saying "Are you sure you want to permanently removethese items?" You are then given the choice to select "OK,"to delete the items, or "Cancel," to prevent the items frombeing removed. Dialog Box***********A movable window that is displayed on screen in response tothe user selecting a menu option. It provides the currentstatus and available options for a particular feature in theprogram. Dialog boxes are typically small, but depending onthe amount of information that must be conveyed, they cansometimes be large.Example:- Changing font in the notepad.
119.wirte the test cases for triangle.Assume that the prg takes inputs as 3 sides of triangle : 1. Enter 0 0 0 : Error : no triangle can be made2. Enter -1 -1 -1 Error : no triangle can be made -ve values3. Enter 1 0 x : Error : no triangle can be made . only numbers and no alhpabets4. Do not enter any values : Prompt to enter valid values 5. Enter 0.000000000000001 , 1000000000000,1000000000000 : Triangle should be made (Boundary value) 6. And the most tricky Enter 1 2 4 : Triangle can not be made . Summation of 2 sides should always greater than third value . 1+2<4 . So triangle can not be made 7. 2 2 2 : Equilateral triangle 8. 1 2 2 : Isoscelous triangle 9. Test with very small values , very large values and
combinations of both .
120.does tester use design document for writing testcasesyes, HLD- higllevel design document from where we write system testcasesLLD-Lowlevel design document from where we write
integraton test cases.
121.what is diffrerence between build and versionRelease if of 2 types- external release and internal releaseExternal release is version where as internal release to testing team is build.
122.Wht is Testing Frame work.Is it same in the Manual and Automation testing. can body can explain it in detail.Usaully in Manual there is no framework. we write testcases in Excel sheet.But for automation every company has itz own framework. i..e we write scripts and save them in a folder and for functions, recoveries,data,object repository for all these
we use different folders.
123.what is test procedureA document providing detailed instructions for the execution
of one or more test cases.
124.What is the format of bug report?The format will be like this1.Defect case id:,Defect description,defect module,defect
type,defect severioty,defect priority
125.Giving the good example for High priority with low severioty bug examle?If a client having some particular logo on the home page,if that logo is missing then the bug status is high priority and low seveority.Because of this bug the functionality is not stopping in the application.But as per client it is very important.So the status will be high priority & low severity.
126.what is the testing process if water fall is the sdlc modelIf the company is following the SDLC Model, the process will be like this1. Requiremnts gathering (SRS)2. Analysis design(Low level design,high level design)3. Coding and Developement4. Testing and Reporting5. Release
6. Maintanence
127.Write the Test Cases for ATM(Any Time Money)Step 1: Check Weather It is displaying the Name correctly after inserting the card Say For Example Welcome Vinodh Step 2: Check weather it is asking for PIN NUMBER Check with exact PIN Number Check bu giving wrong PIN Number Step 3: Check the same with cards already expired or Blocked Step 4: Check is it performing the operations correctly if we enter the exact PIN Number Step 5: Enter the amount more than your available balance
Step 6: After collecting the amount check for available
128.Test cases for Traffic Signals1.First of all we should check for three colours and three direction signalsThe three colours should me red,orange,greensecondly if the signal is red the traffic should stopthirdly if the signal is green the traffic should move and it should the directions that the persons who are going to right should move right if the right arrow single is green if the right direction light is off they should stop and the other direction people should move.In the same manner we should right for other directions also.
2.First check for color First REDSecond YellowThird Green Suppose if there is any time Duration check is signal lights are getting changed automaticallyEnsure that only one light is on at a time Suppose if Pedestrain Crossing is there means Ensure that the lights are ON/OFF Properly based on the signal 129.Any body can explain how do we find Duplicate Defects.1.Duplicate Defects means The same type of defects that are present in defferent places of application bcoz of copy,paste operation of code during the code development process.For example if you take one application it has 9(lets say)screens.But the 9 screens have some identical properties/features.The developpers will write a piece of code then this code will be copied and used where ever they need. During the process of Test case execution if we find any bug we used to enter the the failure result in test caseand we assign a bug id for that. we know that we used to write test case such that for each and every functionality there must be at least one test case. If we find the bug for first time we enter the bug description in defect report and we assign a bug id.if we fined the same bug again already entered bug will be present in the test case result column.
2. Raising the Already existed defect which is in open condition in the defect report log 130.Any body can tell what are the contents RTM(Requirements Tracebility Matrix)RTM(Requirements Tracebility Matrix) Normally RTM is an simple excel sheet with the following columns:1.Requirement ID 2.Requirements description 3.High Level Design(HLD) 4.User Documentation 5.Unit Test Case Id 6.Integration Test Case Id 7.System Test Case Id 8.Release / Build Number Requirement ID will be present in the SRS document.RTM is matrix of test case id's of each level of testing. whehn ever we write test case that test case ID must be ntered into RTM. During the Review process the reviewer will look at the RTMfor checking the testcases completeness against the requirements. 131.what are build and version plz explain why nomber changes in build and version?BUILD:After fixing some number of bugs developmenty people will release the software as a build. VERSION: when the software is added dome new features that release is called version. 132.explain v- model? why we call this model as v-model, not an u-model?1.V stands for Verification and Validation. In V-Model testing is conducted parallel in each phase. During the preparation of SRS documents UAT test cases aredeveloped. During coding stage functional test cases aredeveloped and so on2.V Model stands for Test Stratergy(verfication vs validation) Here Devlopment & Testing Activities are in parallel 133.what is v-model?'V' model is a software devolopment and testing model which helps identify need of planning and design of testing in the early stage of devolopment process.One arms of 'V' model is conventional waterfall model whereas another arm of 'V' shows corresponding testing methodology required at each phase of devolopment process.Here devolopmemt and testing are parallelly done. 134.swap 2 variables without using 3 rd variable?let A=10 B=20after swaping A=20 B=10ok A = A + B (A = 20+10 = 30) B = A - B (B = 20-10 = 10)---->B=10 A = A - B (A = 30-10 = 20)---->A=20 135.Process in ur company??? Y only V?? y not waterfall and spiral??? tell me advantages and disadvantages?we have our won modelv means verificaton& validation at the same timeverification conducted dovelopers and validation conducted testers in v model output give very quality product because testmanagement people involved in teting.dis : it is very costly model,time consumeingadv: very quality water fall model is is also used spiral model is very time consuming process and customer is give the continious requirment the we go to sprial model 136.what is difference between load ,strss and perofrmance??? can u explain me with example?1.one will perform testing on application with some expected load then how to perform the aplication is load testing testing the application with unexpected load in order to ply stress on application in this testing we findout application maximum capacity after that load application may work or may not workperformance testing means with expected & un expected loads how to perform the application 2. Load Test : No of Users access the system(permittes users & below or Above No's) Stress Test: Test The Load Vs volme Performance Test: Check for Response time, throughput & resource consumtion3. Load and Stress Testing are a part of Performance testing. Load Testing: Apply a maximum level of load to the system, i.e, if database then load a maximum no of data in to the table or in case of website try with maximum no of user and see whether the system is satisfying its load level according to the specification. Stress Testing: Apply the maximum stess to the system and see at what level the system crash. i.e, if the specification is to run the system in 128 MB RAM then try running the system in 64 MB RAM and 256 MB RAM and check the stress level.
4. Load Testing: The application is tersted against heavy loadsor inputs such as testing of web sites in order to find out at what point the website/application fails or at what point the its performance degrades Stress Testing : The application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries ect., which checks for the stress/load the application can withstand 137.what is meant by cyclomatic complexity?1.it is used to measure the complexity of software process& itis used to measure how many test cases are passed in the application 2. Cyclomatic Complexity is a software measurement developed by Thomas Macabe. It directly measures linearly independent path of program source code Cyclomatic Complexity = No of Edges - No of Nodes + 2 * Number of connected componentsor alternative Definition G = Edges - Nodes + 2or No of closed loops in the flowgraph + 1 138.How do ensure that we prepared Test cases for all the requiremets.. or how do we ensure that we didn't missed out any requirments...do we prepare any Tracebility matrix..1.for this we use traceability matrix..here we map each requirement with test cases to make sure we didnt miss any requirement.. 2. Not necessarily to use RTM Check the User Business Scenaio given in the document Based on that only we can prepare the Test cases/Test scenarios. In our Unit we do not RTM Missing Functionalities can be catched @ Peer Review or @ Lead Review. 139.What is difference between web application and non-web applications?windowbased app:in this we insatl the application in each and every p.c2:it is two tier architecher3:we make any changes in each and every application web: we instal the application in server side only2:it is generally three or n- tier architear3:we make changes inserver then automatically effected in client side 140.what is the template u used for informing clients regarding known issues when u near to release1.It is not a template,actually it is Release notesRelease notes will contain all the known issues and work arounds.2. Template used is Test Case Design Template.In this we have1)Test case Name(ID)2)Requirement Number3)Module Name4)Precondition5)Seviarity6)Test Data7)Test Case Type8)Breif Description 3. Release Notes contains Known Issues/Known defects while releasig the Build. 141.what ways u followed for defect managementWe are using internal tool Protrack for defect management.With this we can testers enter bugs to the respective project team members who are related to the project
The ways to follow defect management are 1. test plan (what will be defect management system followedin the project)2.Afetr the Test case execution over we can post the defectsin template followed by a company in the company 142.what are the stages in Testing life cycle?The stages in Testing life cycle are:Test IntiationTest PlanningTest DesignTest ExecutionTest ReportRegression Testing (This is conducted on modified build when the bugs found in the existing build)Test Execution closure. 143.what is unit testing? It comes under white box or Black Box testing?Unit testing is Module wise testing of Application. As Unit testing is done by Programmer this testing is done for code testing i.e. White box testing. On the other side Manual testers do manual testing for it i.e. Black Box testingUnit testing is testing individual module fo an application.it is done by developers.it comes under white box testing.In black box testing we test the functinality or behavior of an application.we dont have the internal knowledge of the application.where as in white box testing basic path coverage,loops and funtions written in coding
144.Difference between QA and Testing?QA is nothing but verification.where in focus is giving on prevention of bugs. Testing is validation where in focus is given on dectecting bugs.QA and testing have a very important role in software development life cycle.To make it more clear here is one exampleAssume if a boy studying in 1 std have a aim to be doctor.then one should make sure. The boy passes all the exams from 1 to 10. while taking up 11 he should make sure to take up science rather than arts,commerce. Once this is done make sure he passes his 12th with good number of marks and is qualified for entrance exam.finally when he gets this degress in M.B.B.S . He is a doctor.Watch. the whole process from 1 to his getting M.B.B.S degress is nothing but QA that is quality asssurance.Once the boy is doctor is nothing but Testing. here u r testing wheather the boy is doctor or not. It is as good as saying wheather he passed or failed.In Short QA: Prevention of errors Testing: detection of errors. In detailQA is the process to ensure that all the procedures and standereds are establish and followed throughout the life cycle.Testing is the process to execute the system in both Favorable and unfavorable conditions in order to find the bugs.In favorable conditions it produced the correct results and in unavorable conditions it produced the correct results.
145.what is the difference between Load,Stress and Volume Testing?Load: how the application reacts under heavy loads(done using virtual users)Stress: how the application reacts under peak hours.
Volume: how the application reacts for growing database.
stress testing:what is the max load under the acceptable system performance? load testing, is sometimes called volume testing:what is the max load at the point of the system will be
crashed.
146.what is penetration testing?Penetration testing is nothing but security testing i.ehow well the application provides security against unautorized internal or external access
147.What is smoke testing?Smoke testing in nothing but testing the application whetherall the major functionalities are available in order to dothorough testing. nothing but checking whether build is stable or not..Smoke Testing means testing the most important functionality of the software.
148.What is pairwise testing?All-pairs testing or pairwise testing is a combinatorial testing method that, for each pair of input parameters to a system tests all possible discrete combinations of those parameters.In pairwise testing, two testers combinly working on the same system for the same project.The main aim of pairwise testing is, to exchange of ideas between the testers.The sucess of pairwise testing depends on coordination between the testers.
149.What is concurrency testing?It means Testing the software with anticipated load levels for the purpose of identifying problems in resourse contention, Response times etc.Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
Checking if there are any problems when multiple uses access the code or when a single user opens multiple browers? Not as load testing ..just checking more than a single User
150.What is Data Flow Testing?Data flow testing: Testing in which test cases are designed based on variable usage within the code.This comes under White Box Testing. Data-flow testing looks at the lifecycle of a particular piece of data (i.e. a variable) in an application. By looking for patterns of data usage, risky areas of code can be found and more test cases can be applied. 151.what is volume Testing?testing the software with heavy volumes of data. it is done to findout memory leaks and buffer overflows.Volume Testing:Testing that purposely subjects a system (both hardware and software) to a series of tests where the volume of data being processed is the subject of the test.Such systems can be transactions processing systems capturing real time sales or could be database updates/deletes and or data retrieval or you can say that It is to test the volume of data is acceptable to meet the projected capacity of the organisation'sbusiness
processing.
152.What is driver in testing point of view?Driver is a dummy program used instead of main modulIt acivates connection to sub module. Drivers 4 inpur purposeTest Harness is different, the Environment Consist of Both
Stub and Drivers are called Test harness.
153.what is stub?Explain in testing point of view?A temporary implementation of part of a program for debugging purposes.Stub is a part of Intgeration TestingIntergration Testing1>Top down-Use stubs to test the moduleStub is a dummy module replaced in order to test the main module so that we are sure that the integration between both the modules works fine 2>Bottom Up-- Use driver to test the modulethe test data is sent to main module thru the drivers(also
called Test Harness)
154.what is Regresstion testing? when it will be needed?Regression testing is nothing but executing the same testcases on the different build.it will be needed when an bug was fixed or when a new
functionality is added to existing functionality..I agree with Satya to some extend. To my view Regression Testing is the process of retesting the application after a defect is fixed, to check if due to this fixed, no other problems is caused to its related features. Lets take an example: In our application, there are 10 features,Ft1Ft2Ft3Ft4Ft5Ft6Ft7Ft8Ft9Ft10Lets consider, defects are fixed in Ft4 and Ft8. Now, to run the regression, we have to check which features are inter-related to thefeatures Ft4 and Ft8, say Ft3 & Ft5 for Ft4 and Ft7 & Ft9 for Ft8. Once its identified, the related testcase are identified from Ft3, Ft5, Ft7 and Ft9. And these related testcases are used for running the Regression.Regression Testing run whenever changes are made in the Application. 155.what is parallel testing?Comparing our Product / Application build with other products existing in the market.Parallel Testing is also known as Comparative Testing / Competetive Testing.
We will check the present version of the product with the older versions of the same product.
156.What is endurance testing?Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.it is also called soak testing. it is testing the application under heavy volumes of data for a prolonged period of time
157.Branch testing comes under white box testing or black box testing?Branch testing is done while doing white box testing. where in focus is given on code.There are many other white box technique.Like Loop testing
158.what is the meaning of compatibility testing in view of web application testing?Checking the application on different platforms (Operating System) with different browsers,the main aim of compatibility testing is to test weather application can run successfully on different OS.
159.where testing exactly starts in v-model?
testing starts from requirement stageTestin is maily two type1.static testing2.dyamic testingStating starts from requirment gathering stage.it is in the form of inspection ,reviews,walk throws,pear reviews, ect.dynamic testing starts from unit testing stage.it is actual testing.
160.Do u writing a separate testcase for Regression Testing? If it is Yes, Explain How to write the Testcase?we r not going to write new test cases. We will select the some of the test cases from test case document, and execute the test cases to check for the bug fixes. Here we selecting the test cases such way that, all the basic functionality test cases, and affected bug test cases.
161.how many levels of regression testing is avilable in our testing process?1.Regular Regression2.Full Regression3.Progression TestingIn regular regression every built is tested to verify weather thefixed bugs have any bad impact on other parts of the functionalities.It is done regularly during the testing process evry after getting new built Final regression is done after the complition of fixing all the bugs.It is advisible to have stable built during Final regression testing. 162.how will you decide defect severity & priority?with respective of user we decides the priority and severity of thedefects. Severity is decided by the User requirement, Priority isdecided by the time guide lines to acomplish the taskhow the bug is goin to effect the bussines of the client if its there........... and how soon as a tester you think it has to be fixed.Severity is seriousness of defect wrt functionality.Priority is the importance of defect wrt customer requirment. 163.differentiate defect age & build version control?defectage: The time gap between defect reporting and resolving the defect.builtversioncontrol: The development is assainging a unique versionnumber to every modified build.Build interval period: It is time gap between product delivered to testing team by development team. 164.what will you do when your reported defect rejected?if my defect report is rejected by defect tracking tean then i will explain about that defect's seviority and priority with test lead and if they convience me with their explanation (regarding no need of insertion of that bug)then i will do my remaining testing otherwise i will convienece them with respective user problem. The above answer is fine, But when we cannot convience the TL or the Dev Team about the severity of the Bug it is always adviced to approach the QA for the same. 165.how will you know whether your reported defect rejected?every company follow their own bug tracking tools .So when a bug is posted or rejected a mail will come to repoters and developers involved,and when u will open bug tracker u can get status has changed to rejected . 166.how will you report defects in your company?If we find any defect then we will raise in a defect tracking tool and assigning to the developer in same tool. 167.how many levels of test execution will you follow and describe them?There are five levels of testing which we are following1. Unit Testing2. Integration Testing3. System Testing4. System Integration Testing5. User acceptance testing Note: sometimes we have to follow the one more level of testing i.e. Production Verification testing which is after the UAT.(Depends on client requirement) 168.what is your company testcase format?IEEE 169.what methods will you follow to repare test cases in your organization?Tracebulity matrix is maping between requirements and testcases.it contains Requirements----usecases func-------testcase disg so based on tracebulitymatrix u can repare testcases. 170.differentiate test scenario & test case?Test case is a set test inputs,execution conditions,expected result...etc developed for particular objective(For testing of particular product)...whereasScenario is set of all test cases or scripts and sequences in which they are to be fallowed. 171.what are the key components of test plan document?with respective project size, availablity of test engineers on bench,availability of test duration, identifying tractical risks with respectively lack of time,lack of test engineers knowledge,lack of resources, lack of documentation and sudden changes in customer requirements.Main components of test plan are1.Background(platform)2.Test Items(Programs/modules)3.Features to be testd4.Features not to be tested5.Approach5.Item pass/Fail criteria6.Suspension/resumption criteria7.Test Deliverales8.Testing Tasks9Environmental needs8.Responsibilities9.Staffing & Training10.Schedule11.Resources12.Risks13.Approvals 172.differentiate test strategy and test plan?1.Test strategy defines "what is our approach to test thatproduct/Project" where as the test plan defines "what to test, how to test when to test and who to test".2.Test strategy is a company level document where as test plan is a project level document.
173.what and all i should be prepared for attending the software testing interview,because iam confused with how to get prepared,please some one tell me the main topics to get prepared for it. 1.Concentrate and understand on basic testing definitions and terminology. 2.understand the SDLC life cycle models Like:Water fall model V-model Spiral model V-V model...etc 3.Understand the basic testing life cycle and testing levels . 4.Try to acquire some knowledge from ur friends on real time testing and responsibilities..etc 5.Test case preparation 6.Types test cases 7.Test plan preparation 8.Types of test plan 9.Defect reporting both manual and automated using tools like test director and clear case. 10.Know about metrics
11.Know about traceability matrix...etc
174.what type of bugs u found commonly in ur project?Exceptional errors, Error messages are not clear and proper, Functional errors etc....
175.How do you decide when you have 'tested enough?'When the 90% of requirements are covered , Maximum defects are rectified except (some)low level defects are not covered , customer satisfy that project and time is less, then we are closing the testing.1. When u crossed the budget2. When u have tested all the testcase
3. When u fullfulled the requirements
176.Why does user inter-operability testing present such a big challenge to the testing effort?Inter Operatability is to Check the transfer of Software (or) Application from one Hardware configuration to another Hardware configuration .
177.What is difference between Regression and Restesting?Retesting:Testing the same test case again and again after the bug fixedRegression: For the number of test case in the module to be tested after executing the test cases for that module if any requirement changes we need to execute the entire test case for the particular module changedRetesting :running a test morethan onceRegression testing:It is a test used to verify that already tested software is still functioning correctly or not and not affected by the test object and the environment.The main aim of regression testing is to check whether it has any unexpected side effects after fixing a bug.what we can conclude is if regression testing is a super-set then retesting is a subsetReTesting: The Re-Execution of a test on same applicationbuild with multiple test data is called ReTesting.Regression Testing: the reexecution of a test on modifiedbuild to ensure bugfix work and possibilities of side effectoccurance .Consider an Example.you have modules like add, delete, modify, cancel and ok buttons.you have already 150 test cases for the above.Now You are going to introduce an other module ie, edit, for this You have 50 test cases.After integrated edit with other modules, you check 50 test cases working correctly or not. This is Regression Testing,Now all together you should check all the 150 + 50 test cases, ie called Retesting.
178.What is Boundary Value Analysis(BVA) and Equivalence Class Partition(ECP)?BVA : If an input is bounded on 20 and 30 , the testcase should included the values 20 , 30 and Just above and below of 20,30 respectively.ECP : if an input specified member of sets , then one valid and one invalid values includedEquivalence partitioning:- It is an black box testing technique and it can be defined as "Dividing the input domain of data into the class of interavels and from which we can prepare test cases. Boundary value analysis:- It is also an black box technique majorly stress on boundary conditions.As the most of the bugs reside at boundaries.BVA: Instead of we entering every possible input domain wecheck the input domains with boundaries only.Eg:empID takes 4-16 alphabets.value - status.min->4 passmin-1->3 failmin+1->5 passmax->16 passmax-1->15 passmax+1->17 fail. ECP:with this we enter valid values enter as input domains. Eg:empID should accept 4-16 alphabets.valid - invalida-z 0-9
A-Z spaces, special characters.
179.Tell me the situation where sanity test cases should pass and smoke test cases fail...?We do sanity or smoke test when we receive the build for the first time. Before accepting the build we test the basic functionality of the build. This process is called either sanity of smoke. Both are alomost similar.
Sanity testing->Testing the application for the first time.Or it is called an adhoc testing.Not in a position to test the application in details.Smoke testing-Testing only the major functionalities of the application.Smoke testing is done when ever a new build is happening.Or it is an example of regression test.Usually we can use automation testing tools for performing smoke testing.Situation-->A new build has been released(New version).The new changes implemented by the development team has been tested and is working fine(Sanity testing).But due to the new changes,Some existiong functionalities is getting failed(Smoke testing).First clear with sanity and smoke.Smoke testing: its also called as build verification test. As soon as we get the build we are testing whether the build is in testable condition or not.Sanity testing: Its testing the major functionalities in the application. You ll go for sanity if u dont find enough time to do full regression test. so there is no chance for sanity to pass, if smoke fails.sanity test checks the existence of functionality where as smoke test checks whether functionality is working or not ..since smoke test checks the functionalities work so the test cases which passed during sanity test will sometime 180.What is the input for System testing?For the system testing input is the documents of system specifiction.Here in system testing we check the functionality and usability of the entire system as a whole.System testing takes input as all the software components that have successfully passed integration testing and also the software system itself integrated with any hardware systems.
181.what is the difference between test case and test script?Test case is a descrption what data to be tested and what data to be inserted what are the actions to be done to check actual result against expected resultWhat are the actual inputs we will use? What are the expected results? is called test scriptTest Script: Is a short program written in a programming language used to test part of the functionality of the software system.a written set of steps that should be performed manually can also be called a test script,however this is more correctly called a test case.Both are same but terminology varies according to Context.Test case term is used in manual testing where as test script(test case)is generated by an automation tool.
182.Difference b/w test case and scenarios.1. when srs come from client , on the basis of tht documentuse cases are generated mainly by developer,then on basis ofthis scenarios are generated , then test cases are formed.it is not necessary tht scenarios are made , many projectrequires only test cases.Test Scenario: Identifying the all possible areas to be tested (What)Test Case: describes an input action and expected result to ensure that a certain feature works correctly as per the specifications.
183.What is TRR ?Test Result Record..consists of Failed test casesBug descriptionTest description
184.write test cases on calculatorTC1: Does the calculator turn on when teh on button is pressedTC2: Does it display the number on teh screen that was pressedTC3: If we enter 2 and then the plus symbol "+" and thenenter2 again,then does it display the answer "4" or not.TC4: Same way for all the buttons like *,/,-,%, square rootsand allTC5: When we press the clear button then is the screendisplay reduced to "0" or not
185.what will be the test case for car & Cell phoneTest Cases for Car :-1)The lock should be open by its defined key.2)All the lights should be working correctly.3)The gears shold be working properly.4)All three padels break,clutch and accelerator must be working accurately.5)The fuel consumption should not be high.6)The wheels should follow the stering. Test Cases for Cell Phone :-1)All the keys are working properly or not.2)Is it getting locked or unlocked by the defined keys.3)It should catch the network properly.4)It should support all the cards(sim).5)If it is vibrator enabled phone then its vibrator is working with the ringtone or not.6)Is it connecting with the desired number which we have dialed.
186.Define the term Bug, Failure, Error?Error: Functionality is MissingBug:Functionality is there,but not working properly if a software performance is not up to the mark or expectations of the Customer,we can say that its a failure.Most of the times,Error and Bug are of same ,but they differentiate in their definitionBug is an error in developer point of view.Defect is an error in tester point of view.Failure is an error in customer point of view. Developer - Tester - Client/end user
BUG DEFECT FAILURE
187.diff between water fall model and v-model?Waterfall model:in this type of model the flow is sequential starting from the planning ,design,coding and after that testing is put into effect .so the testing is after the coding only and not before tha V-Model:in this model the testing starts after business requirements is finished and furnished and testing continues in paralled with the codingso that we can eliminate error in the earlier stageIn the waterfall model we have single phase testing.That should be after completion of code.In the v-model we have mutiple phase testing,in every phase we should use testing
188.What is Black Box testing and who is responsible for Black box testing?Without knowing the internal knowledge of the applicatin ifyour r doing testing it comes under Black Box testing..Testers are responsible for thisBlack box testing is the testing the functionality of the application and the one who is creative in thinking in different prospectives can test the applicationblack box testing focus on functional requirements of the software.this type of testing method attempts to find incorrect or missing functions, errors in datastructure or external database acces,initialaisation and termination errors. black box testing is conducted on integrated functional components whose design integrity has been verified through completion of traceble white box testing. black box testing method focus on system externals. black box testing method creates testcaes based on system externals. here we test the software without know how it is working.we are blindly testing the software thats why we call it as black box testing.this is also called behavioural testing ,here we test the behaviuor of the application. this is also called as functional testing . test engineers are responsible for black box testing
189.What is meant by system testing?after finishing integeration testing system testing will carried out.the combined of the software is tested for its functionality and perfofmance requirements.
190.Explain stress.load,performance and volume testing with example..Performance testing is to check the applications ,i.e. responce time, processing speed,efficiency.LOAD TEST: testing done by increasing the number of users gradually at a specific time.STRESS TEST: Testing done with maximum number of user that system can hold in low disk space, low memory, low configuration.
VOLUME TESTING: Maximum data that the sysyem can accomudate.
191.there are 100 test cases. and u got a bug at 85th test cases. u reported it to dev and dev fixed that bug. when u r doing regression testing from whic test case u'll do tetsing?? will start from 85 th test case are u'll execute 100 test cases??
from 85th test casea) In regration testing is in that build what are the before the defect it solved or not any new requirements are add or not, if any changes or done this build this type of test here donewe will execute from 85 th test case only. unless it has impact on the previous testcases.we will do the ReTest of 85th Test case & will close the Bug IF Requirement is Satisfied.ThenWe will do the Regression Testing of The All 100 Test Casesbased on Test Scenario's.(i.e we will execute 100 test cases).Regression Testing is to check the Retested Bug should not have Impact on other passed Test cases.Should be checking which functionalities get effected due to the bug.then select those TCs for regression testing.Continue from 85th TC and include the above TCs to it and complete the testing.we will perform retest on the modified build by executing 85th test case.Also we will select some related test cases which may affect the modified area and perform regression testing.First we will test the failed test cases . because that defects are alredy fixed by development team.. after that we will go for regression testing , in that also we will select some of the test cases (core functionality).first of all what do u mean by regression testing?already tested functionality is tested again to check whether right functionality (original functionality) is not affected, that is regression testing ,now in this case we will test from 1st test case till 85th test case , from 86th test case onwards it not regression testing
192.diffrence between application testing and product testing?Product testing means when any company does testing fortheir own (company's) product ex... Nortan AntVirus is theSymantec's product; if Symantec test the Nortan ie. calledas the Product testing.Where as if any company take some projects from some othercompanies like ABC company takes projects from IBM and testthat project on some charges ie called as Application Testing.
193.Who assign Bug Id & Bug Version Id?Bug ID is assigned by the Defect tracking tool which u r using. About Bug Version Id, I don't what it means.
194.what is role of the tester in an organaisation and project? what is the daily work of tester?Daily Work of a Tester.1. Design Test cases.2. Execute Test cases.3. Bug or Defect Tracking.4. Test Report.
5. Co-ordination To Prepare Test Plan.(Optional).The daily work of the tester depends on day to day activities.1) At the time of requirements the tester role would be going through the requirements, prepare use cases and test scenarios based on BRS.2) At the Design Phase,the tester role would be in preparing the test plan and test cases.3) At the coding stage the tester will be getting builds and according to the test cases he has to test the applcation in all areas.If a bug is found, he has to report to the developer and keep tracking the defects from build to build. 4) Daily he has to report the bugs and the applcation status through test reports. 5) Clarify the doubts regarding the applciation through query log document to be sent to client.
195.Difference between Verification & Validation?Verifiaction:Means are we doing right thing.i.e we have to check whether we are implementing right process.validation:Means are we doing things right.i.e we have to check whether we have developed a software as per the client requirementVerification is done through out the life cycle of the project/product where as validation comes in the testing
phase of the application.
196.please give me the template of tracebility matrix ? i need whicch is commanly used in real time...Following ten columns will be the in Traceability matrix.1.Requirement ID( the Requirement id provided in the SRS document) 2.Requirements (Requirement Descrition)3.High Level Design (document reference) 4.Implementation Design(implemented or not) 5.Source Code (Component/class Program Name) 6.User Documentation(preparation) 7.Unit Test Case Id(Unit test case ID's) 8.Integration Test Case Id (Integration test case ID's)9.System Test Case Id (System Test case Id's)10.Release / Build Number(build release number)It will give coverage of Testcases at different levels of
Testing.
197.what is defect?defect is defined in two ways1) from producer pointb of view 2) from customer point of view from producer point of defect is deviation from desired output. from customer point of view application that cause customer dissatisfaction. defects are recorded for 4 major purposes 1) to correct the defects 2) to know the status of the aplication 3)to develop the defect expectation in future aplication 4) to maintain the quality of the application. sa person makes an error it causes fault in the software it
result failure in operation.
198.what is the difference between Test strategy and test plan?Test plan : After completion of SRS learning and business requirement gathering test management concentrate on test planning,this is done by Test lead, or Project lead. Test Strategy : Depends on corresponding testing policy quality analyst finalizes test Responsibility Matrix.this is done by QA. but both r Documents. TEST PLAN : We describe what to Test ? 1.Scope.2.Approach.3.What are the modules to test. TEST STATERGY : We describe How to Test ?
We define the methodology ?test strategy is part of test plan.*test plan describes how to test the application. *test strategy describes what the technoques we are going
to follow.
Test Plan: Test Plan describes What to Test, How to Test andWhen to Test. It is a document which describes the scope ofa software testing project.Test Strategy: It is a document which describes the overalltesting approach.
199.what is the scalability testingHere are the Opinions of the some of the allinterview users posted in previous on Scalability Testing..1.scalabilty is nothing but how many users that the application should handle2.Scalability is nothing but maximum no of users that the system can handle3.Scalability testing is a subtype of performance test where performance requirements for response time, throughput, and/or utilization are tested as load on the SUT is increased over time.4.as a part of scalability testing we test the expandability of the application.in scalability we test 1.Applicaation scalability 2.Performance scalabilityApplication scalability: to test the possibility of implementing new features in the system or updating the existing features of the system. with the help of design doc we do this testingPerformance scalability: to test how the s/w perform when it is subjected to varying loads to measure and to evaluate the the performance behaviour and the ability fo the s/w to continue to function properly under different workloads. --> to check the comfort level of an application in terms of user load. and user experience and system tolerance levels--> the point within an application that when subjected to increasing workload begin to degrade in terms of end user experience and system tolerance--> response time execution time system resource utilization network delays
è stress testing
Scalability is nothing but measurement, the metrics. it is
mostly bound to the performance
200.can any one give the example for high severity high priority high severity low priority low severity high priority low severity low priorityThe examples are posted several times posted in this site.Pls.check the previous discussions in this allinterview site. use search words like 'severity', 'priority' in the search
provided in the site.SEVERITY-1.SHOW STOPPER-UNINSTALL THE PRODUCT,DATA CORRUPTION.2.HIGH-FUNCTION IS NOT WORKING ACC TO SPEC.3.MEDIUM-INCORRECT DATA,INCORRECT MESSAGE ERROR.4.LOW-MISSPELLINGS,INCORRECT GRAMMICTAL. PRIORITY-1.SHOW STOPPER-IMMEDIATE FIX,VERY VISIBLE.2.HIGH-MUST FIX BEFORE PRODUCT IS RELEASED.MEDIUM-SHOULD FIX IF TIME PERMITS.
LOW-WOULD LIKE FIX BUT CAN RELEASED AS
201.What are the concepts of networking and database ,a software tester should know?i think there is not neccesary to have the knowledge of networking,but we should have a min knowledge of database i think upto Joins is enough but its good if we know triggers,stored procedures also.
because we will b handling database check points....
202.how do you test me?Behavioral aspects of a human: Appearance,Color, Way of dressing, Body language, Way of speaking, Knowledge on subject,Qualifications, Skills,adaptability..etc
i will test you in the above following aspectsFirst tell me the requirements.
After that i will tell u.
203.Actually by using severity u should know which one u need to solve so what is the need of priority?I guess severity reflects the seriousness of the bug where as priority refers to which bug should rectify first. ofcourse if the severity is high the same case is with priority in normal.severity decided by the tester where as priority decided by developers. which one need to solve first knows through priority not with severity.how serious of the bug knows through severity. 204.what is the testing process if water fall is the sdlc modelIf the company is following the SDLC Model, the process will be like this1. Requiremnts gathering (SRS)2. Analysis design(Low level design,high level design)3. Coding and Developement4. Testing and Reporting5. Release6. Maintanence
Branch Testing:In an ideal world every branch of every component would be fully tested. However, in the real world this hardly ever happens.In branch/decision testing every possible branch is tested, regardless of the outcome. Compare this to Statement testing, where if there is no statement on the branch, it is not tested.
Why?1) To find faults 2) Give credible information about the state of the component, on which business decisions can be taken.
Who?Idealy an independent person or body, to the one that wrote the code. Usually, however it is conducted by the developer.
Where?As close as possible to the point where the code was written.
When?As part of component testing.
How?Each test case, the following should be specified:-
1) Inputs to the component 2) Decision or branch to be executed 3) Expected outcome.
A metric branch decision coverage is available to measure how much of the code has been executed.
Webspiders Testing
1.What is software testing
2.Testing Services & Types
3.Technology Based Software Testing
3.Testing Life Cycle
4.Delivery Model
5.Test Deliverables & Metrics
6.Testing Tool Capabilities
What is software testingThe goal of the testing activity is to find as many errors as possible before the user of the software finds them. We can use testing to determine whether a program component meets its requirements. To accomplish its primary goal (finding errors) or any of its secondary purposes (meeting requirements), software testing must be applied in a systematic fashion. Testing involves operation of a system or application under controlled conditions and evaluating the results.
Verification and Validation
Verification and Validation (V&V) is a Software Testing activity to enhance quality of the software being built. It is planned and conducted systematically through out the software lifecycle.
Verification is the checking or testing of items, including software, for conformance and consistency with an associated specification. Software testing is just one kind of verification, which also uses techniques such as reviews, analysis, inspections and walkthroughs.
Validation is the process of checking that what has been specified is what the user actually wanted. Validation activity may begin when most or all software functions as per customer expectations. Validation testing provides final assurance that the software meets all functional, behavioral and performance requirements. Usually Black-box testing is used for this activity.
Verification: Are we building the Project right?
Validation: Are we building the right product?
Debugging vs TestingThe term bug is often used to refer to a problem or fault in a computer. There are software bugs and hardware bugs.
Software testing should not be confused with debugging. Debugging is the process of analyzing and locating bugs when software does not behave as expected. Although the identification of some bugs will be obvious from playing with the software, a methodical approach to software testing is a much more thorough means of identifying bugs. Debugging is therefore an activity, which supports testing, but cannot replace testing. However, no amount of testing can be guaranteed to discover all bugs.
Common Problems
Poor requirements – if requirements are unclear, incomplete, too general, or not testable, there will be problems
Unrealistic schedule – if too much work is crammed in too little time, problems are inevitable
Inadequate testing – no one will know whether or not the program is any good until the customer complains or systems crash
Requirements change – requests to pile on new features after development is underway are common
Miscommunication – if developers don’t know what is needed or customers have erroneous expectations, problems are guaranteed
Poorly documented code – sufficient comments not built into the source code, requirement changes not updated in the impacted documents
Solutions
Solid requirements – clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players use prototypes to help nail down requirements.
Realistic schedules – allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.
Adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing.
Stick to initial requirements as much as possible – be prepared to defend against excessive changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, use rapid prototype during the design phase so that customer can see what to expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on.
Communication – require walkthroughs and inspections when appropriate; make extensive use of group communication tools - e-mail, groupware, networked bug-tracking tools and change management tools, intranet capabilities, etc.; ensure that information/documentation is available and up-to-date - preferably electronic, not paper; promote teamwork and cooperation; use prototypes early on so that customers' expectations are clarified.
Testing Services & Types WS Testing Practice provides a wide services portfolio, from Unit Testing right up to Application Certification. In general testing services can be categorized into three main types, such as:
Functional Testing
Non-Functional Testing
Automated Testing - for both functional and non-functional testing
Competitive Analysis Testing
Functional Testing
Testing developed application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team. Functional testing covers
Unit Testing
Smoke testing / Sanity testing
Integration Testing (Top Down, Bottom up Testing)
Interface & Usability Testing (including Independent Focus Groups)
System Testing
Regression Testing
Pre User Acceptance Testing (Alpha & Beta)
User Acceptance Testing
White Box Testing, Black Box Testing
Globalization and Localization Testing (Regional Settings, Languages etc.)
WS’s Testing Practice has 300+ person-years of experience across various types ofFunctional testing.
Non-Functional Testing
Testing the application based on the clients and performance requirement. Non-functioning testing is done based on the requirements and test scenarios defined by the client. Non-functional testing covers
Load and Performance Testing
Ergonomics Testing
Stress & Volume Testing
Compatibility & Migration Testing
Data Conversion Testing
Security / Penetration Testing
Operational Readiness Testing
Installation Testing
Security Testing (Application Security, Network Security, System Security)
Web Spiders Testing Practice has 175+ person-years of experience across various types of Non-Functional testing.
Automated Testing
Automated testing is an art of converting manual test cases to machine executable code. The output of a test automation project is a (or a set of) test suite, which will be used by testers to verify the application time and again. Test automation is perceived as an efficiency improvement program, which will improve time to market advantage for product development organization.
Automated Testing is automating the manual testing process currently in use. This requires that a formalized "manual testing process" exist in the company or organization. Minimally, such a process includes:
Detailed test cases, including predictable "expected results", which have been developed from Business Functional Specifications and Design documentation.
A standalone Test Environment, including a Test Database that is restorable to a known constant, such that the test cases are able to be repeated each time there are modifications made to the application.
Web Spiders Testing Practice has 60+ person-years of Automation Testing experience.
Competitive Analysis Testing
Competitive Analysis can be defined as usability, functionality or a performance evaluation whereby two or more competitive products are compared by simulating an environment where the products are going to be used. (e.g. IE Vs Netscape, Oracle DB Vs. SQL Server Vs DB2)
Web Spider’s Competitive Analysis Testing ensures that your product fits in perfectly in its competitive market. Our analysis matrix makes sure that you get the most out of the analysis, whether you are a manufacturer or a buyer. For Product developers our benchmark testing services provide results that form the basis for quality improvement or as a sales tool to show superiority of their products. For buyers, it’s an effective way to help them make the right purchase decision.
Before starting our analysis, we ensure that the right measurement parameters are identified on the basis of which the analysis is carried out. In order to understand this, we encourage the active participation of our customers. Once these are decided, our QA experts do the rest.
Technology Based Software Testing
1. GUI testingTesting Considerations for GUI Communication; aspects to be tested are:• Tool tips and status bar
Missing information• Enable/ Disable toolbar buttons• Wrong/ misleading/ confusing information• Help text and Error messages• Training documents
Dialog Boxes; aspects to be tested are: • Keyboard actions• Mouse actions• Canceling• Okaying• Default buttons• Layout error• Modal• Window buttons• Sizable• Title/ Icon• Tab order• Display layout• Boundary conditions• Sorting• Active window• Memory leak
Command structure; aspects to be tested are: • Menus• Popup menus• Command Line Parameters• State transitions
Program rigidity; aspects to be tested are: • User options• Control• OutputPreferences; aspects to be tested are: • User tailor-ability • Visual preferences • Localization
Usability; aspects to be tested are: • Accessibility• Responsiveness• Efficiency• Comprehensibility• User scenarios• Ease of use
Localization; aspects to be tested are: • Translation• English-only dependencies• Cultural dependencies• Unicode• Currency• Date/ Time• Constants• Dialog contingency
2. Application Testing
Testing Considerations for Application Testing
Applications
Testing
C, C++ Applications
Memory leak detection
Code coverage
Static and dynamic testing
Test coverage analysis
Runtime error detection
Automated component testing
Measurement of maintainability, portability, complexity, standards compliance
Boundary conditions testing
Java Applications/ Applets
Automated component testing
Functional testing
Performance testing
Applet/ application testing
Code coverage
Boundary conditions testing
Win 32-based Applications
Memory leak detection of win32 programs
Performance testing
Stress testing of Windows applications and system clients
3. Application Programming Interface (API) testing
Testing Considerations/ Issues
The following tasks can be automated:
1. Test-code builds
2. Test-suites execution
3. Report generation
4. Report publishing
5. Report notification
6. Periodic execution of test-suites
7. A tool for test automation should be identified very early in the project.
8. A simulator (that services the API calls) should be developed by the testing team. In the absence of this simulator, there is a dependency on a Server (not developed by the API development team).
Validating the APIs for user-friendliness:
· Meaningful names
· Concise and short names
· Number of arguments
· Easy-to-read names
4. Middleware Testing
· Functional testing
· Interoperability testing
· Performance testing
5. Database/ Backend (and database applications) testing
Testing Considerations/ Issues
Apart from testing (verify/ validate this) the application the following needs to be considered for databases:
· Distributed Environment
· Performance
· Integration with other systems
· Security Aspects
Description/ Sub-tasks
Boundary conditions testing (Data); aspects to be tested:
· Dataset
· Numeric
· Alpha
· Numerosity
· Field size
· Data structures
· Timeouts
Accuracy/ Integrity testing (Data); aspects to be tested:
Boundary conditions testing (Data); aspects to be tested:
· Calculations - Reports
· Calculations - Backend
· Divide by zero
· Truncate
· Compatibility
· Test data
· Data consistency
Database connectivity; aspects to be tested:
Database connectivity; aspects to be tested:
· Save
· Retrieval
Database schema testing; aspects to be tested:
Database connectivity; aspects to be tested:
· Databases and devices
· Tables, Fields, Constraints, Defaults
· Keys and Indices
· Stored procedures
· Error messages
· Triggers, Update
· Triggers, Insert
· Triggers, Delete
· Schema comparisons
Security testing; aspects to be tested
Security testing; aspects to be tested
· Login and User security
6. Web Site/ Page Testing
Applications
Testing
Link and HTML Testing
Detecting HTML compatibility problems
Checking Cascading Style Sheets
Checking link and content
Checking HTML syntax/ Validating HTML documents
Detecting broken/ dead links
Web site performance analysis
Functional Testing
Web site functional testing
Testing for completeness and consistency of web pages
Performance Testing
Load testing of web based systems
Reliability, performance and scalability testing of web applications
Load and performance testing of web server
Testing Life Cycle WEB SPIDERS has a well-defined testing Lifecycle, which is applicable to all testing scenarios. The lifecycle ensures that all the relevant inputs are obtained, the planning is adequately carried out and the executions are as per plan.In addition the results are obtained reviewed and monitored. The lifecycle also defines the interfaces into the overall Quality management processes and also the Project delivery phases.
The testing life cycle can be broadly classified into three different life cycle models depending upon the type of application and the test strategy used such as:
Application Testing Life Cycle
Automation Testing Life Cycle
Package Testing Life Cycle
Application Testing life cycle
This life cycle is used for standard applications that are built from various custom technologies and follow the normal or standard testing approach. The Application or custom-build Lifecycle and its phases is depicted below:
Test Requirements
• Requirement Specification documents• Functional Specification documents • Design Specification documents (use cases, etc) • Use case Documents • Test Trace-ability Matrix for identifying Test Coverage
Test Planning
• Test Scope, Test Environment• Different Test phase and Test Methodologies• Manual and Automation Testing• Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc• Evaluation & identification – Test, Defect tracking tools
Test Environment Setup
• Test Bed installation and configuration• Network connectivity’s• All the Software/ tools Installation and configuration• Coordination with Vendors and others
Test Design
• Test Traceability Matrix and Test coverage• Test Scenarios Identification & Test Case preparation• Test data and Test scripts preparation• Test case reviews and Approval• Base lining under Configuration Management
Test Automation
• Automation requirement identification• Tool Evaluation and Identification.• Designing or identifying Framework and scripting• Script Integration, Review and Approval• Base lining under Configuration Management
Test Execution and Defect Tracking
• Executing Test cases• Testing Test Scripts• Capture, review and analyze Test Results• Raised the defects and tracking for its closure
Test Reports and Acceptance
• Test summary reports• Test Metrics and process Improvements made• Build release• Receiving acceptance
Automation Testing life cycle
Advantages of this automated software using the above AST life cycle.
High Quality to market
Low Time to market
Reduced testing time
Consistent test procedures
Reduced QA costs
Improved testing productivity
Improved product quality
AST Requirements
• Requirement / Functional Specification documents• Design Specification documents (use cases, etc)• Test Traceability Matrix for identifying Test Coverage• Functional/ Non-Functional and test data requirements• Test phases to be automated and % of automation
AST Planning
• Automated Software Testing (AST) Scope• Tool Evaluation and identification• AST Methodologies and Framework• Prepare and Base lining Scripting standard and ASTPlan
AST Environment Setup
• AST Test Bed installation and configuration• Network connectivity’s• All the Software/ tools Licenses, Installation and configuration• Coordination with Vendors and others
AST Design
• Test Script and test data preparation• Test scripts / test data review and unit testing• Integration Testing Test scripts and testing• Base lining under Configuration Management
AST Execution and Defect Tracking
• Executing AST Test Suit• Capture, review and analyze Test Results• Defects reporting and tracking for its closure
AST Maintenance Reports and Acceptance
• AST Results and summary reports• Test Metrics and process Improvements made• Base lining of AST Test suits/ scripts/ test date etc for maintenance phase• Getting Acceptance
Package Testing life cycle
Testing life cycle followed for all the packaged applications like Oracle, SAP, Siebel, CRM tools, Supply Chain management applications, etc are detailed in the below diagram.
Project Preparation
• Identifying the business processes• Organization of the project team• Setting up the communication channel• Kick start the project• Identifying the infrastructure availability• Reporting structure and project co-ordination
Business Blueprinting
• Requirement Study• Identifying the business rules• Mapping the business processes• Identify the test conditions• Setting up the test environment for the system• Forms the input needed for the configurations
Realization
• Configuration & Customization • Activating the business rules • Development of certain flows • Identifying certain flows not in the standard • Forming the system configurations • Unit Testing
Final Preparation
• Uploading the master data • End user training • Simulating all the flows • Tie-up between interfaces • Operational Readiness Testing and UAT • Sign-off
Cut over, Go-live and Support
• Migrate to new system • Transfer all legacy business applications • Communicate deployment status. • Support new system • Transfer ownership to system owner • Take customer acceptance after production deployment
Delivery Model
Given below is the generic service delivery model followed by Web Spiders Practice.
ONSITE
• Resources at onsite location • Complete project execution onsite • Project reporting to Onsite Manager
ONSITE - OFFSHORE
• Resources at onsite and offshore locations • Project execution at both onsite and offshore• Project transition to offshore • Project reporting to Offshore Manager • Project backed by proven processes methodologies and support functions
OFFSHORE
• Entire project execution offshore • Project reporting to Offshore Manager • All the Software/ tools Installation and configuration• Project backed by proven processes methodologies and support functions
Web Spiders selects the ideal delivery model based on each customer’s specific business case.
A very high-level workflow of the interaction process between the customer and Web Spiders is illustrated below:
1. The client sends the introductory mail mentioning the outline of the QA job that he/she is looking for.
2. The QA Manager goes through it and responds with a set of queries.
3. The client responds and asks for the test plan and sample test cases.
4. The QA Manager prepares the test plan and mails it along with a few sample test cases.
5. The test plan is reviewed and finalized by both the parties.
6. The QA Manager discusses the project with the team members and the test cases are prepared.
7. Test cases are executed for a particular version of the product, reviewed and mailed to the client.
8. The bugs are approved by the client and debugged by his/her development team.
9. Depending on the project requirements, the client releases the next version of the project for QA and the test plan and test cases are updated, accordingly.
10. The same process is repeated.
Once all the bugs have been reported, and the project is re-tested and de-bugged, the QA process concludes
Test Deliverables & Metrics
Test Deliverables
There are different test deliverables at every phase of the SDLC. These deliverables are provided based on the requirement once before the start of the test phase and there are other deliverables that are produced towards the end/after completion of each test phase. Also there are several test metrics that are collected at each phase of testing. Below are the details of the various test deliverables corresponding to each test phase along with their test metrics.
The standard deliverables provided as part of testing are:
Test Trace-ability Matrix
Test Plan
Testing Strategy
Test Cases (for functional testing)
Test Scenarios (for non-functional testing)
Test Scripts
Test Data
Test Results
Test Summary Report
Release Notes
Tested Build
Test Metrics
There are several test metrics identified as part of the overall testing activity in order to track and measure the entire testing process. These test metrics are collected at each phase of the testing life cycle /SDLC and analyzed and appropriate process improvements are determined and implemented as a result of these test metrics that are constantly collected and evaluated as a parallel activity together with testing both for manual and automated testing irrespective of the type of application. The test metrics can be broadly classified into the following three categories such as:
1. Project Related Metrics – such as Test Size, # of Test Cases tested per day –Automated (NTTA), # of Test Cases tested per day –Manual (NTTM), # of Test Cases created per day – Manual (TCED), Total number of review defects (RD), Total number of testing defects (TD), etc
2. Process Related Metrics – such as Schedule Adherence (SA), Effort Variance (EV), Schedule Slippage (SS), Test Cases and Scripts Rework Effort, etc.
3. Customer related Metrics – such as Percentage of defects leaked per release (PDLPR), Percentage of automation per release (PAPR), Application Stability Index (ASI), etc.
Testing Tool Capabilities
1. Automated testing tools
Sample Tools described below:
Sl.No.
Tool Name
Type of testing
Vendor
1
Quick Test Professional
Functional and Regression
Mercury Interactive Inc.
2
Silk Performer
Load, Stress and Performance
Segue Software
3
Silk Test
Functional and Regression
Segue Software
4
WinRunner 6.2
Functional and Regression
Mercury Interactive Inc.
5
Test director
Effective test management
Mercury Interactive Inc.
6
Rational Robot
GUI
Rational and IBM
7
Rational suite Test Studio
Functional and test control
Rational and IBM
8
Clear Case
Configuration Management and change control (version)
Rational and IBM
9
Rational Rose
Unit / Design changes and reengineering
Rational and IBM
10
QA Wizard
Web based applications or Web sites, Windows applications, or Java applications
Seapine Software
2. Test management tools
These are some of the tools that are used to plan, manage and track the testing activities, with their corresponding vendors such as:
Sl.No.
Test Management Tool
Vendor
1
Test director
Mercury
2
Test Manager
Rational
3
QA Director
Compuware
This page contains summary descriptions of a number of load and performance tests. It also contains links to more detailed pages, containing additional information including diagrams, tables, examples and screen dumps for a variety of load and performance tests.
Load Tests
Load Tests are end to end performance tests under anticipated production load. The primary objective of this test is to determine the response times for various time critical transactions and business processes and that they are within documented expectations (or Service Level Agreements - SLAs). The test also measures the capability of the application to function correctly under load, by measuring transaction pass/fail/error rates. This test is one of the most fundamental load and performance tests and needs to be well understood.
This is a major test, requiring substantial input from the business, so that anticipated activity can be accurately simulated in a test situation. If the project has a pilot in production then logs from the pilot can be used to generate ‘usage profiles’ that can be used as part of the testing process, and can even be used to ‘drive’ large portions of the Load Test.
Load testing must be executed on “today’s” production size database, and optionally with a “projected” database. If some database tables will be much larger in some months time, then Load testing should also be conducted against a projected database. It is important that such tests are repeatable as they may need to be executed several times in the first year of wide scale deployment, to ensure that new releases and changes in database size do not push response times beyond prescribed SLAs.
Failover Tests (click here for more details on Failover Testing)
Failover Tests verify of redundancy mechanisms while under load. For example, such testing determines what will happen if multiple web servers are being used under peak anticipated load, and one of them dies. Does the load balancer react quickly enough? Can the other web servers handle the sudden dumping of extra load? This sort of testing allows technicians to address problems in advance, in the comfort of a testing situation, rather than in the heat of a production outage.
Soak Tests (a.k.a. Endurance Testing) (click here for more details on Soak Testing)
Soak testing is running a system at high levels of load for prolonged periods of time. A soak test would normally execute several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed. Also, due to memory leaks and other defects, it is possible that a system may ‘stop’ working after a certain number of transactions have been processed. It is important to identify such situations in a test environment.
Stress Tests (click here for more details on Stress Testing)
Stress Tests determine the load under which a system fails, and how it fails. This is in contrast to Load Testing, which attempts to simulate anticipated load. It is important to know in advance if a ‘stress’ situation will result in a catastrophic system failure, or if everything just “goes really slow”. There are various varieties of Stress Tests, including spike, stepped and gradual ramp-up tests. Catastrophic failures require restarting various infrastructure and contribute to downtime, a stress-full environment for support staff and managers, as well as possible financial losses. This test is one of the most fundamental load and performance tests and needs to be well understood.
Targeted Infrastructure Test (click for details on Targeted Infrastructure Testing)
Targeted Infrastructure Tests are Isolated tests of each layer and or component in an end to end application configuration. It includes communications infrastructure, Load Balancers, Web Servers, Application Servers, Crypto cards, Citrix Servers, Database… allowing for identification of any performance issues that would fundamentally limit the overall ability of a system to deliver at a given performance level.
Each test can be quite simple, For example, a test ensuring that 500 concurrent (idle) sessions can be maintained by Web Servers and related equipment, should be executed prior to a full 500 user end to end performance test, as a configuration file somewhere in the system may limit the number of users to less than 500. It is much easier to identify such a configuration issue in a Targeted Infrastructure Test than in a full end to end test.
Performance Tests (click for more details on Performance Testing)
Performance Tests are tests that determine end to end timing (benchmarking) of various time critical business processes and transactions, while the system is under low load, but with a production sized database. This sets ‘best possible’ performance expectation under a given configuration of infrastructure. It also highlights very early in the testing process if changes need to be made before load testing should be undertaken. For example, a customer search may take 15 seconds in a full sized database if indexes had not been applied correctly, or if an SQL 'hint' was incorporated in a statement that had been optimized with a much smaller database. Such performance testing would highlight such a slow customer search transaction, which could be remediated prior to a full end to end load test.
Network Sensitivity Tests (click for more details on network sensitivity tests)
Network sensitivity tests are tests that set up scenarios of varying types of network activity (traffic, error rates...), and then measure the impact of that traffic on various applications that are bandwidth dependant. Very 'chatty' applications can appear to be more prone to response time degradation under certain conditions than other applications that actually use more bandwidth. For example, some applications may degrade to unacceptable levels of response time when a certain pattern of network traffic uses 50% of available bandwidth, while other applications are virtually un-changed in response time even with 85% of available bandwidth consumed elsewhere.
This is a particularly important test for deployment of a time critical application over a WAN.
Volume Tests (click for more details on volume testing)
Volume Tests are often most appropriate to Messaging, Batch and Conversion processing type situations. In a Volume Test, there is often no such measure as Response time. Instead, there is usually a concept of Throughput.
A key to effective volume testing is the identification of the relevant capacity drivers. A capacity driver is something that directly impacts on the total processing capacity. For a messaging system, a capacity driver may well be the size of messages being processed. For batch processing, the type of records in the batch as well as the size of the database that the batch process interfaces with will have an impact on the number of batch records that can be processed per second.
Sociability (sensitivity) Tests
Sensitivity analysis testing can determine impact of activities in one system on another related system. Such testing involves a mathematical approach to determine the impact that one system will have on another system. For example, web enabling a customer 'order status' facility may impact on performance of telemarketing screens that interrogate the same tables in the same database. The issue of web enabling can be that it is more successful than anticipated and can result in many more enquiries than originally envisioned, which loads the IT systems with more work than had been planned.
Tuning Cycle Tests
A series of test cycles can be executed with a primary purpose of identifying tuning opportunities. Tests can be refined and re-targeted 'on the fly' to allow technology support staff to make configuration changes so that the impact of those changes can be immediately measured.
Protocol Tests
Protocol tests involve the mechanisms used in an application, rather than the applications themselves. For example, a protocol test of a web server may will involve a number of HTTP interactions that would typically occur if a web browser were to interact with a web server - but the test would not be done using a web browser. LoadRunner is usually used to drive load into a system using VUGen at a protocol level, so that a small number of computers (Load Generators) can be used to simulate many thousands of users.
Thick Client Application Tests
A Thick Client (also referred to as a fat client) is a purpose built piece of software that has been developed to work as a client with a server. It often has substantial business logic embedded within it, beyond the simple validation that is able to be achieved through a web browser. A thick client is often able to be very efficient with the amount of data that is transferred between it and its server, but is also often sensitive to any poor communications links. Testing tools such as WinRunner are able to be used to drive a Thick Client, so that response time can be measured under a variety of circumstances within a testing regime.
Developing a load test based on thick client activity usually requires significantly more effort for the coding stage of testing, as VUGen must be used to simulate the protocol between the client and the server. That protocol may be database connection based, COM/DCOM based, a proprietary communications protocol or even a combination of protocols.
Thin Client Application Tests
An internet browser that is used to run an application is said to be a thin client. But even thin clients can consume substantial amounts of CPU time on the computer that they are running on. This is particularly the case with complex web pages that utilize many recently introduced features to liven up a web page. Rendering a page after hitting a SUBMIT button may take several seconds even though the server may have responded to the request in less than one second. Testing tools such as WinRunner are able to be used to drive a Thin Client, so that response time can be measured from a users perspective, rather than from a protocol level.
Friday, September 28, 2007
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment