Software Testing Interview Questions.....
General Testing Interview Questions
Q. What is a good test case ?
A: — A good test case is effective. That is, it will find a fault. This does not mean that a test case that does not find a fault is not a good one, since this implies that the fault that the test case could have found is not present (i.e. it gives us some confidence in the software, and this in itself has value). Perhaps we should say that a good test case has the potential to find a fault.
~ A good test case is exemplary; meaning that it does more than one thing for us (is capable of finding more than one fault).
~ A good test case is evolvable. As the software changes so too will some of the tests need changing to reflect different functionality, new features, etc. The effort to update test cases is usually very significant. However, much can be done when designing test cases to reduce or minimise the amount of maintenance effort needed to update test cases to make them compatible with later versions of the software.
~ A good test case is economic. A test case that requires 50 people to come into the office on a Saturday ~ morning and all be poised at their keyboards at 9am is expensive to perform and it can only be run once a week. A test case that can be run at the touch of a button and only lasts two seconds is much more economic.
We should design test cases to be economic, evolvable, exemplary and effective. However, we often need to design a balance between effective/exemplary and evolvable Economic.
Q. What Kinds of Testing should be considered?
A: — Some important testing types are :
Black box testing: Not based on any knowledge of internal design or code.Tests are based on requirements and functionality
White box testing: Based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, and conditions.
Unit testing: The most ‘micro’ scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
Incremental integration testing: Continuous testing of an application as new functionality is added; requires that various aspects of an applications functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
Integration testing: Testing of combined parts of an application to determine if they function together correctly the ‘parts’ can be code modules, individual applications, client and server applications on a networked. This type of testing is especially relevant to client/server and distributed systems.
Functional testing: Black-box type testing geared to functional requirements of an application; testers should do this type of testing. This does not mean that the programmers should not check their code works before releasing it(which of course applies to any stage of testing).
System testing: Black –box type testing that is based on overall requirements specifications; covers all combined parts of system.
End to end testing: Similar to system testing; the ‘macro’ end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing: Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5minutes warrant further testing in item current state.
Regression testing: Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.
Acceptance testing: Final testing based on specifications of the end-user or customer, or based on use by end users/customers over some limited period of time.
Load testing: Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
Stress testing: Term often used interchangeably with ‘load’ and ‘performance’ testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repletion of certain actions or inputs input of large numerical values, large complex queries to a database system, etc.
Performance testing: Term often used interchangeable with ‘stress’ and ‘load’ testing. Ideally ‘performance’ testing (and another ‘type’ of testing) is defined in requirements documentation or QA or test plans.
Usability testing: Testing for ‘user-friendlinesses’. Clearly this is subjective,and will depend on the targeted end-ser or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used programmers and testers are usually not appropriate as usability testers.
Install/uninstall testing: Testing of full, partial, or upgrade install/uninstall processes.
Recovery testing: Testing how well a system recovers from crashes, hardware failures or other catastrophic problems.
Security testing: Testing how well system protects against unauthorized internal or external access, damage, etc, any require sophisticated testing techniques.
Compatibility testing: Testing how well software performs in a particular hardware/software/operating/system/network/etc environment.
Exploratory testing: Often taken to mean a creative, informal software test that is not based on formal test plans of test cases; testers may be learning the software as they test it.
Ad-hoc testing: Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software testing it.
User acceptance testing: Determining if software is satisfactory to an end-user or customer.
Comparison testing: Comparing software weakness and strengths to competing products.
Alpha testing: Testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
Beta testing: Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
Mutation testing: Method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes (‘bugs’) and retesting with the original test data/cases to determine if the ‘bugs’ are detected proper implementation requires large computational resources.
Q. What is the Difference between client server testing and web server testing??
A: —Web systems are one type of client/server. The client is the browser, the server is whatever is on the back end (database, proxy, mirror, etc). This differs from so-called “traditional” client/server in a few ways but both systems are a type of client/server. There is a certain client that connects via some protocol with a server (or set of servers).
Also understand that in a strict difference based on how the question is worded, “testing a Web server” specifically is simply testing the functionality and performance of the Web server itself. (For example, I might test if HTTP Keep-Alives are enabled and if that works. Or I might test if the logging feature is working. Or I might test certain filters, like ISAPI. Or I might test some general characteristics such as the load the server can take.) In the case of “client server testing”, as you have worded it, you might be doing the same general things to some other type of server, such as a database server. Also note that you can be testing the server directly, in some cases, and other times you can be testing it via the interaction of a client.
You can also test connectivity in both. (Anytime you have a client and a server there has to be connectivity between them or the system would be less than useful so far as I can see.) In the Web you are looking at HTTP protocols and perhaps FTP depending upon your site and if your server is configured for FTP connections as well as general TCP/IP concerns. In a “traditional” client/server you may be looking at sockets, Telnet, NNTP, etc.
Go to Top
E-learning Testers Interview Questions
- What is SCORM?
- What is Sec 508?
- Have you done any portal testing?
- DO you have any idea about LMS or LCMS?
- Have you done any compliance testing
- Have you done any compatibility testing?
- What are the critical issues found while testing the projects in your organization?
- Tell me about the testing procedures used by you in your organization?
- How do you test a flash file?
- Have you found any difference while testing a flash file and Html file?
- What types of testing are you aware of?
- While doing the compatibility testing have you found any critical issues?
- While doing the compliance testing has you noticed any critical/ abnormal issues?
- What is the procedure you use while doing the Regression testing in your projects?
- Have you done any performance or stress testing in your testing? If yes have you used any automation techniques in that or not?
- Are you aware of any bug tracking tools for defect tracking?
- Tell me about the testing scenario’s used in project?
- Have you written any test cases/test plan? If yes can you tell me one or two instances in that?
- Have you aware of any Usability and Acceptance testing?
- Is your testing conventional or non-conventional?
- Have you done any other lang’s courses testing? If yes have you faced any critical situations?
- What are things to be more concentrated while testing same projects on different environments?
- What are AICC standards?
Go to Top
Q What is Impact analysis? How to do impact analysis in your project?
A: — Impact analysis means when we r doing regressing testing at that time we r checking that the bug fixes r working properly, and by fixing these bug other components are working as per their requirements r they got disturbed.
Q. How to test a website manualy?
A: — Web Testing
During testing the websites the following scenarios should be considered.
Functionality
Performance
Usability
Server side interface
Client side compatibility
Security
Functionality:
In testing the functionality of the web sites the following should be tested.
Links
Internal links
External links
Mail links
Broken links
Forms
Field validation
Functional chart
Error message for wrong input
Optional and mandatory fields
Database
Testing will be done on the database integrity.
Cookies
Testing will be done on the client system side, on the temporary internet files.
Performance:
Performance testing can be applied to understand the web site’s scalability, or to benchmark the performance in the environment of third party products such as servers and middle ware for potential purchase.
Connection speed:
Tested over various Networks like Dial up, ISDN etc
Load
What is the no. of users per time?
Check for peak loads & how system behaves.
Large amount of data accessed by user.
Stress
Continuous load
Performance of memory, cpu, file handling etc.
Usability :
Usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction. Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as opposed to becoming an additional impediment to such accomplishment. The broad goal of usable systems is often assessed using several
Criteria:
Ease of learning
Navigation
Subjective user satisfaction
General appearance
Server side interface:
In web testing the server side interface should be tested.
This is done by Verify that communication is done properly.
Compatibility of server with software, hardware, network and database should be tested.
The client side compatibility is also tested in various platforms, using various browsers etc.
Security:
The primary reason for testing the security of an web is to identify potential vulnerabilities and subsequently repair them.
The following types of testing are described in this section:
Network Scanning
Vulnerability Scanning
Password Cracking
Log Review
Integrity Checkers
Virus Detection
Performance Testing
Performance testing is a rigorous usability evaluation of a working system under realistic conditions to identify usability problems and to compare measures such as success
rate, task time and user satisfaction with requirements. The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing.
To conduct performance testing is to engage in a carefully controlled process of measurement and analysis. Ideally, the software under test is already stable enough so that this process can proceed smoothly. A clearly defined set of expectations is essential for meaningful performance testing.
For example, for a Web application, you need to know at least two things:
expected load in terms of concurrent users or HTTP connections
acceptable response time
Load testing:
Load testing is usually defined as the process of exercising the system under test by feeding it the largest tasks it can operate with. Load testing is sometimes called volume testing, or longevity/endurance testing
Examples of volume testing:
testing a word processor by editing a very large document
testing a printer by sending it a very large job
testing a mail server with thousands of users mailboxes
Examples of longevity/endurance testing:
testing a client-server application by running the client in a loop against the server over an extended period of time
Goals of load testing:
Expose bugs that do not surface in cursory testing, such as memory management bugs, memory leaks, buffer overflows, etc. Ensure that the application meets the performance baseline established during Performance testing. This is done by running regression tests against the application at a specified maximum load.
Although performance testing and load testing can seen similar, their goals are different. On one hand, performance testing uses load testing techniques and tools for measurement and benchmarking purposes and uses various load levels whereas load testing operates at a predefined load level, the highest load that the system can accept while still functioning properly.
Stress testing:
Stress testing is a form of testing that is used to determine the stability of a given system or entity. This is designed to test the software with abnormal situations. Stress testing attempts to find the limits at which the system will fail through abnormal quantity or frequency of inputs.
Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it (in which case it is sometimes called negative testing).
The main purpose behind this madness is to make sure that the system fails and recovers gracefully — this quality is known as recoverability.
Stress testing does not break the system but instead it allows observing how the system reacts to failure. Stress testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail gracefully?
Is it able to recover from the last good state on restart?
Etc.
Compatability Testing
A Testing to ensure compatibility of an application or Web site with different browsers, OS and hardware platforms. Different versions, configurations, display resolutions, and Internet connect speeds all can impact the behavior of the product and introduce costly and embarrassing bugs. We test for compatibility using real test environments. That is testing how will the system performs in the particular software, hardware or network environment. Compatibility testing can be performed manually or can be driven by an automated functional or reg The purpose of compatibility testing is to reveal issues related to the product& interaction session test suite.with other software as well as hardware. The product compatibility is evaluated by first identifying the hardware/software/browser components that the product is designed to support. Then a hardware/software/browser matrix is designed that indicates the configurations on which the product will be tested. Then, with input from the client, a testing script is designed that will be sufficient to evaluate compatibility between the product and the hardware/software/browser matrix. Finally, the script is executed against the matrix,and any anomalies are investigated to determine exactly where the incompatibility lies.
Some typical compatibility tests include testing your application:
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip drives, USBs, etc.)
Q which comes first test strategy or test plan?
A:– Test strategy comes first ans this is the high level document…. and approach for the testing starts from test strategy and then based on this the test lead prepares the
test plan….
Q what is the difference between web based application and client server application as a testers point of view?
A:– According to Tester’s Point of view—--
1) Web Base Application (WBA)is a 3 tier application ;Browser,Back end and Server.
Client server Application(CSA) is a 2 tier Application ;Front End ,Back end .
2) In the WBA tester test for the Script error like java script error VB script error etc, that shown at the page. In the CSA tester does not test for any script error.
3) Because in the WBA once changes perform reflect at every machine so tester has less work for test. Whereas in the CSA every time application need to be instal hence ,it maybe possible that some machine has some problem for that Hardware testing as well as software testing is needed.
Q What is the significance of doing Regression testing?
A:– To check for the bug fixes. And this fix should not disturb other functionality
To Ensure the newly added functionality or existing modified functionality or developer fixed bug arises any new bug or affecting any other side effect. this is called regression test and ensure already PASSED TEST CASES would not arise any new bug.
Q. What are the different ways to check a date field in a website?
A:– There are different ways like :–
1) you can check the field width for minimum and maximum.
2) If that field only take the Numeric Value then check it’ll only take Numeric no other type.
3) If it takes the date or time then check for other.
4) Same way like Numeric you can check it for the Character,Alpha Numeric aand all.
5) And the most Important if you click and hit the enter key then some time pag e may give the error of javascript, that is the big fault on the page .
6) Check the field for the Null value etc
The date field we can check in different ways Possitive testing: first we enter the date in given format
Negative Testing: We enter the date in invalid format suppose if we enter date like 30/02/2008 it should display some error message and also we use to check the numeric or text
Go to Top
Q Give ex of high severity, low priority bug? A: — A page is rarely accessed, or some activity is performed rarely but that thing outputs some important Data incorrectly, or corrupts the data, this will be a bug of H severity L priority
Q If project need to be released in 3 months what type of Risk analysis you do in Test plan?
A:– Use risk analysis to determine where testing should be focused. Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
• Which functionality is most important to the project’s intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio
Q. What are the possible Test cases for IE 6.0 ?
A:– Test cases for IE 6.0 i.e Internet Explorer 6.0:--
1)First I go for the Installation side, means that –
+ is it working with all versions of Windows ,Netscape or other softwares in other words we can say that IE must check with all hardware and software parts.
2) Secondly go for the Text Part means that all the Text part appears in frequent and smooth manner.
3) Thirdly go for the Images Part means that all the Images appears in frequent and smooth manner.
4) URL must run in a better way.
5) Suppose Some other language used on it then URL take the Other Characters, Other than Normal Characters.
6)Is it working with Cookies frequently or not.
7) Is it Concerning with different script like JScript and VBScript.
8)HTML Code work on that or not.
9) Troubleshooting works or not.
10) All the Tool bars are work with it or not.
11) If Page has Some Links, than how much is the Max and Min Limit for that.
12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled .
13) Is it working with the Uninstallation Process.
14) Last but not the least test for the Security System for the IE 6.0
Q. Where you involved in testing life cycle ,what type of tests have you performed ?
A:– Generally test engineers involved from entire test life cycle i.e, test plan, test case preparation, execution, reporting. Generally system testing, regression testing, adhoc testing
etc.
Q. what is Testing environment in your company ?
A:– testing process is going as follows
quality assurance unit
quality assurance manager
testlead
test engineer
Q. who prepares the use cases?
A:– In Any company except the small company Business analyst prepares the use cases
But in small company Business analyst prepares along with team lead
Q. What methodologies have you used to develop test cases?
A:– generally test engineers uses 4 types of methodologies
1. Boundary value analysis
2.Equivalence partition
3.Error guessing
4.cause effect graphing
Go to Top
Q. Why we call it as a regression test not retest?
A:– If we test whether defect is closed or not i.e Retesting But here we are checking the impact also regression means repeated times
Q. Is automated testing better than manual testing. If so, why?
A:– Automated testing and manual testing have advantages as well as disadvantages
Advantages: It increase the efficiency of testing process speed in process
reliable
Flexible
disadvantage’s
Tools should have compatibility with our development or deployment tools needs lot of time initially If the requirements are changing continuously Automation is not suitable
Manual: If the requirements are changing continuously Manual is suitable Once the build is stable with manual testing then only we go 4 automation
Disadvantages:
It needs lot of time
We can not do some type of testing manually
E.g Performances
Q. what is the exact difference between a product and a project.give an example ?
A:– Project Developed for particular client requirements are defined by client Product developed for market Requirements are defined by company itself by conducting market survey
Example
Project: the shirt which we are interested stitching with tailor as per our specifications is project
Product: Example is “Ready made Shirt” where the particular company will imagine particular measurements they made the product
Mainframes is a product
Product has many mo of versions
but project has fewer versions i.e depends upon change request and enhancements
Q. Define Brain Stromming and Cause Effect Graphing? With Eg?
A:– BS:
A learning technique involving open group discussion intended to expand the range of available ideas
OR
A meeting to generate creative ideas. At PEPSI Advertising, daily, weekly and bi-monthly brainstorming sessions are held by various work groups within the firm. Our monthly I-
Power brainstorming meeting is attended by the entire agency staff.
OR
Brainstorming is a highly structured process to help generate ideas. It is based on the principle that you cannot generate and evaluate ideas at the same time. To use brainstorming, you must first gain agreement from the group to try brainstorming for a fixed interval (eg six minutes).
CEG :
A testing technique that aids in selecting, in a systematic way, a high-yield set of test cases that logically relates causes to effects to produce test cases. It has a beneficial side effect in pointing out incompleteness and ambiguities in specifications.
Q. Actually by using severity you should know which one you need to solve so what is the need of priority?
A:– I guess severity reflects the seriousness of the bug where as priority refers to which bug should rectify first. of course 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.
severity is nothing impact of that bug on the application. Priority is nothing but importance to resolve the bug yeah of course by looking severity we can judge but sometimes high severity bug doesn’t have high priority At the same time High priority bug don’t have high severity
So we need both severity and priority
Q. What do you do if the bug that you found is not accepted by the developer and he is saying its not reproducible. Note:The developer is on site?
A:– once again we will check that condition with all reasons. then we will attach screen shots with strong reasons. then we will explain to the project manager and also explain to the client when they contact us
Sometimes bug is not reproducible it is because of different environment suppose development team using other environment and you are using different environment at this situation there is chance of bug not reproducing. At this situation please check the environment in the base line documents that is functional documents if the environment which we r using is correct we will raise it as defect We will take screen shots and sends them with test procedure also
Go to Top
Q. what is the difference between three tier and two tier application?
A:– Client server is a 2-tier application. In this, front end or client is connected to
‘Data base server’ through ‘Data Source Name’,front end is the monitoring level.
Web based architecture is a 3-tier application. In this, browser is connected to web server through TCP/IP and web server is connected to Data base server,browser is the monitoring level. In general, Black box testers are concentrating on monitoring level of any type of application.
All the client server applications are 2 tier architectures.
Here in these architecture, all the “Business Logic” is stored in clients and “Data” is stored in Servers. So if user request anything, business logic will b performed at client, and the data is retrieved from Server(DB Server). Here the problem is, if any business logic changes, then we
need to change the logic at each any every client. The best ex: is take a super market, i have branches in the city. At each branch i have clients, so business logic is stored in clients, but the actual data is store in servers.If assume i want to give some discount on some items, so i
need to change the business logic. For this i need to goto each branch and need to change the business logic at each client. This the disadvantage of Client/Server architecture.
So 3-tier architecture came into picture:
Here Business Logic is stored in one Server, and all the clients are dumb terminals. If user requests anything the request first sent to server, the server will bring the data from DB Sever and send it to clients. This is the flow for 3-tier architecture.
Assume for the above. Ex. if i want to give some discount, all my business logic is there in Server. So i need to change at one place, not at each client. This is the main advantage of 3-tier architecture.
Some QA testing questions
1. What is SQA Activities?
2. How can we perform testing without expected results?
3. Which of the following statements about regression testing are true?
a. Regression Testing must consist of a fixed set of tests to create a baseline
b. Regression Testing should be used to detect defects in new features
c. Regression Testing can be run on every build
d. Regression Testing should be targeted to areas of high risk and known code change
e. Regression Testing, when automated, is highly effective in preventing defects
4. How do you conduct boundary analyst testing for “ok”pushbutton
5. What is an exit and entry criteria in a Test Plan ?
6. To whom you send test deliverables?
7. What is configuration Management?
8. Who writes the Business requirements? What you do when you have the BRD?
9. What we normally check for in the Database Testing?
10. What is walk through and inspection?
11. What are the key elements for creating test plan?
12. How do you ensure the quality of the product?
13. What is the job of Quality assurance engineer? Difference between the testing & Quality Assurance job.
14. Can any one send information regarding manual testing. I know just how to use winrunner load runner tool with sample flight reservation application. can any one send me the information how to test web logic and web sphere.
15. What are the demerits of winrunner?
16. How you used white box and block box technologies in your application?
17. What is the role of QA in a project development?
18. How can u test the white page ?
19. How do you scope, organize, and execute a test project?
20. What is the role of QA in a company that produces software?
21. Describe to me when you would consider employing a failure mode and defect analysis?
22. In general, how do you see automation fitting into the overall process of testing?
23. How do you decide when you have ‘tested enough?’
24. Describe to the basic elements you put in a defect report?
25. What is use case? What is the difference between test cases and use cases?
26. What is the importance of a requirements traceability in a product testing?
27. If the actual result doesn’t match with expected result in this situation what should we do?
28. Explain about Metrics and types of metrics like schedule variance , effort variance?
29. What is the difference between functional testing & black box testing?
30. What is heuristic checklist used in Unit Testing?
31. What is the difference between System Testing,Integration Testing & System Integration Testing?
32. How to calculate the estimate for test case design and review?
33. What is Requirements Traceability ? What is the purpose of it ? Explain types of traceability matrices ?
34. What are the contents of Risk management Plan? Have you ever prepared a Risk Management Plan ?
35. What metrics used to measure the size of the software?
Q. If we have no SRS, BRS but we have test cases does you execute the test cases blindly or do you follow any other process?
A: — Test case would have detail steps of what the application is supposed to do. SO
1) Functionality of application is known.
2) In addition you can refer to Backend, I mean look into the Database. To gain more knowledge of the application
Q. How to execute test case?
A: — There are two ways:
1. Manual Runner Tool for manual execution and updating of test status.
2. Automated test case execution by specifying Host name and other automation pertaining details.
Q. Difference between re testing and regression testing?
A: — Retesting:
Re-execution of test cases on same application build with different input values is retesting.
Regression Testing:
Re-execution of test cases on modifies form of build is called regression testing…
Q. What is the difference between bug log and defect tracking?
A: — Bug log is a document which maintains the information of the bug where as bug tracking is the process.
Q. Who will change the Bug Status as Deffered?
A: — Bug will be in open status while developer is working on it Fixed after developer completes his work if it is not fixed properly the tester puts it in reopen After fixing the bug properly it is in closed state.
Q. wht is smoke testing and user interface testing ?
A: — Smoke Testing:
Smoke testing is non-exhaustive software testing, as pertaining that the most crucial functions of a program work, but not bothering with finer details. The term comes to software testing from a similarly basic type of hardware testing.
User Iinterface Testing:
I did a bit or R n D on this…. some says it’s nothing but Usability testing. Testing to determine the ease with which a user can learn to operate, input, and interpret outputs of a system or component.
Smoke testing is nothing but to check whether basic functionality of the build is stable or not?
I.e. if it possesses 70% of the functionality we say build is stable.
User interface testing: We check all the fields whether they are existing or not as per the format we check spelling graphic font sizes everything in the window present or not|
Go to Top
Q. what is bug, deffect, issue, error?
A: — Bug: — Bug is identified by the tester.
Defect:– Whenever the project is received for the analysis phase ,may be some requirement miss to get or understand most of the time Defect itself come with the project (when it comes).
Issue: — Client site error most of the time.
Error: — When anything is happened wrong in the project from the development side i.e. called as the error, most of the time this knows by the developer.
Bug: a fault or defect in a system or machine
Defect: an imperfection in a device or machine;
Issue: An issue is a major problem that will impede the progress of the project and cannot be resolved by the project manager and project team without outside help
Error:
Error is the deviation of a measurement, observation, or calculation from the truth
Q. What is the difference b/w functional testing and integration testing?
A: — functional testing is testing the whole functionality of the system or the application whether it is meeting the functional specifications
Integration testing means testing the functionality of integrated module when two individual modules are integrated for this we use top-down approach and bottom up approach
Q. what type of testing do you perform in a organization while you do System Testing, give clearly?
A: — Following are the types of testing performed:
Functional testing
User interface testing
Usability testing
Compatibility testing
Model based testing
Error exit testing
User help testing
Security testing
Capacity testing
Performance testing
Sanity testing
Regression testing
Reliability testing
Recovery testing
Installation testing
Maintenance testing
Accessibility testing, including compliance with:
Americans with Disabilities Act of 1990
Section 508 Amendment to the Rehabilitation Act of 1973
Web Accessibility Initiative (WAI) of the World Wide Web
Consortium (W3C)
Q. What is the main use of preparing Traceability matrix and explain the real time usage?
A: — A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they are based and the product tested to meet the requirement.
A traceability matrix is a report from the requirements database or repository.
Q. How can you perform the following 1) Usability testing 2) scalability Testing
A:–
UT:
Testing the ease with which users can learn and use a product.
ST:
It’s a Web Testing defn.allows web site capability improvement.
PT:
Testing to determine whether the system/software meets the specified portability requirements.
Q. What does u mean by Positive and Negative testing & what is the diff’s between them. Explain with an example?
A: — Positive Testing: Testing the application functionality with valid inputs and verifying that output is correct
Negative testing: Testing the application functionality with invalid inputs and verifying the output.
Difference is nothing but how the application behaves when we enter some invalid inputs suppose if it accepts invalid input the application
Functionality is wrong
Positive test: testing aimed to show that s/w work i.e. with valid inputs. This is also called as “test to pass’
Negative testing: testing aimed at showing s/w doesn’t work. Which is also know as ‘test to fail” BVA is the best example of -ve testing.
Q. what is change request, how do you use it?
A: — Change Request is a attribute or part of Defect Life Cycle.
Now when u as a tester finds a defect n report to ur DL…he in turn informs the Development Team.
The DT says it’s not a defect it’s an extra implementation or says not part of req’ment. Its newscast has to pay.
Here the status in ur defect report would be Change Request
I think change request controlled by change request control board (CCB). If any changes required by client after we start the project, it has to come thru that CCB and they have to approve it. CCB got full rights to accept or reject based on the project schedule and cost.
Go to Top
Q. What is risk analysis, what type of risk analysis you did in your project?
A: — Risk Analysis:
A systematic use of available information to determine how often specified events and unspecified events may occur and the magnitude of their likely consequences
OR
procedure to identify threats & vulnerabilities, analyze them to ascertain the exposures, and highlight how the impact can be eliminated or reduced
Types :
1.QUANTITATIVE RISK ANALYSIS
2.QUALITATIVE RISK ANALYSIS
Q. What is API ?
A:– Application program interface
Q. What is bug life cycle?
A: — New: when tester reports a defect
Open: when developer accepts that it is a bug or if the developer rejects the defect, then the status is turned into “Rejected”
Fixed: when developer make changes to the code to rectify the bug…
Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned into “Closed” and if the problem resists again, it’s “Reopen
Q. What is deferred status in defect life cycle?
A: — Deferred status means the developer accepted the bus, but it is scheduled to rectify in the next build
Q. What is smoke test?
A; — Testing the application whether it’s performing its basic functionality properly or not, so that the test team can go ahead with the application
Q. Do you use any automation tool for smoke testing?
A: - Definitely can use.
Q. What is Verification and validation?
A: — Verification is static. No code is executed. Say, analysis of requirements etc. Validation is dynamic. Code is executed with scenarios present in test cases.
Q. What is test plan and explain its contents?
A: — Test plan is a document which contains the scope for testing the application and what to be tested, when to be tested and who to test.
Q. Advantages of automation over manual testing?
A: — Time, resource and Money
Q. What is ADhoc testing?
A: — AdHoc means doing something which is not planned.
Q. What is meant by release notes?
A: — It’s a document released along with the product which explains about the product. It also contains about the bugs that are in deferred status.
Q. Scalability testing comes under in which tool?
A: — Scalability testing comes under performance testing. Load testing, scalability testing both r same.
Q. What is the difference between Bug and Defect?
A: — Bug: Deviation from the expected result. Defect: Problem in algorithm leads to failure.
A Mistake in code is called Error.
Due to Error in coding, test engineers are getting mismatches in application is called defect.
If defect accepted by development team to solve is called Bug.
Go to Top
Q. What is hot fix?
A: — A hot fix is a single, cumulative package that includes one or more files that are used to address a problem in a software product. Typically, hot fixes are made to address a specific customer situation and may not be distributed outside the customer organization.
Bug found at the customer place which has high priority.
Q. What is the difference between functional test cases and compatability testcases?
A: — There are no Test Cases for Compatibility Testing; in Compatibility Testing we are Testing an application in different Hardware and software. If it is wrong plz let me know.
Q. What is Acid Testing??
A: — ACID Means:
ACID testing is related to testing a transaction.
A-Atomicity
C-Consistent
I-Isolation
D-Durable
Mostly this will be done database testing.
Q. What is the main use of preparing a traceability matrix?
A: — To Cross verify the prepared test cases and test scripts with user requirements.
To monitor the changes, enhance occurred during the development of the project.
Traceability matrix is prepared in order to cross check the test cases designed against each requirement, hence giving an opportunity to verify that all the requirements are covered in testing the application.
Covansys
1. What is bidirectional traceability ??? and how it is implemented
2. What is Automation Test frame work ?
3. Define the components present in test strategy
4. Define the components present in test plan
5. Define database testing ?
6. What is the difference between QA and QC ….
7. What is the difference between V&V
8. What are different types of test case that u have written in your project..
9. Have u written Test plan ?….
SQL
1. What is joins and define all the joins …
2. What is Foreign key ?
3. Write an SQL query if u want to select the data from one block which intern reflects in another block ?
Unix
1. Which command is used to run an interface?
2. How will you see the hidden file ?
3. What is the command used to set the date and timings …
4. Some basic commands like copy, move,delete ?
5. Which command used to the go back to the home directory ….
6. Which command used to view the the current directory
Go to Top
Virtusa
Testing
1. Tell me about Yourself?
2. Testing process followed in your company …
3. Testing Methodology
4. Where u maintains the Repositories?
5. What is CVS?
6. Bug Tool used?
7. How will you prepare traceability matrix if there is no Business Doc and Functional Doc?
8. How will you validate the functionality of the Test cases, if there is no business requirement document or user requirement document as such…
9. Testing process followed in your company?
10. Tell me about CMM LEVEL -4 …what are steps that to be followed to achieve the CMM -IV standards?
11. What is Back End testing?
12. What is Unit Testing?
13. How will u write test cases for an given scenario…i.e. main page, login screen, transaction, Report Verification?
14. How will u write traceability matrix?
15. What is CVS and why it is used?
16. What will be specified in the Defect Report…?
17. What is Test summary Report…?
18. What is Test Closure report…?
19. Explain Defect life cycle…
20. What will be specified in the Test Case…
21. What are the Testing methodologies that u have followed in your project ?
22. What kind of testing that u have been involved in and explain about it….
23. What is UAT Testing?
24. What is joins and what are the different types of joins in SQL and explain the same?
25. What is Foreign Key in SQL…?
KLA Tencor
1. Bug life cycle?
2. Explain about the Project. …And draw the architecture of your project?
3. What are the different types of severity?
4. Defect tracking tools used?
5. what are the responsibilities of an tester?
6. Give some example how will you write the test cases if an scenario involves Login screen.
AztecSoft
1. What are the different types of testing followed …..
2. What are the different levels of testing used during testing the application?
4. What type of testing will be done in Installation testing or system testing?
5. What is meant by CMMI …what are different types of CMM Level?
6. Explain about the components involved in CMM-4 level
7. Explain about Performance testing ?
8. What is Traceability matrix and how it is done ?
9. How can you differentiate Severity and Priority based on technical and business point of view.
10. What is the difference between Test life cycle and defect life cycle ?
11. How will u ensure that you have covered all the functionality while writing test cases if there is no functional spec and there is no KT about the application
Go to Top