Jmeter Q & A

JMeter Interview Questions have been designed specially to get you acquainted with the nature of questions you may encounter during your interview for the subject of JMeter. As per my experience good interviewers hardly plan to ask any particular question during your interview, normally questions start with some basic concept of the subject and later they continue based on further discussion and what you answer:
Q: What is JMeter?
A: JMeter is one of the Java tools which is used to perform load testing client/server applications. Apache JMeter is open source software, a 100% pure Java desktop application designed to load test functional behavior and measure performance of the application. It was originally designed for testing Web Applications but has since expanded to other test functions.
Q: What is Performance Testing?
A: This test sets the ‘best possible’ performance expectation under a given configuration of infrastructure. It also highlights early in the testing process if changes need to be made before application goes into production.
Q: What is Load Test?
A: This test is basically used for exercising\discovering the system under the top load it was designed to operate under.
Q: What is Stress Test?
A: This test is an attempt to break the system by overwhelming its resources.
Q: What are the protocols supported by JMeter?
A: The protocols supported by JMeter are:
• Web: HTTP, HTTPS sites 'web 1.0' web 2.0 (ajax, flex and flex-ws-amf)
• Web Services: SOAP / XML-RPC
• Database via JDBC drivers
• Directory: LDAP
• Messaging Oriented service via JMS
• Service: POP3, IMAP, SMTP
• FTP Service
Q: List some of the features of JMeter.
A: Following are some of the features of JMeter:
• Its free. Its an open source software.
• It has simple and intuitive GUI.
• JMeter can load and performance test many different server types: Web - HTTP, HTTPS, SOAP, Database via JDBC, LDAP, JMS, Mail - POP3
• It is platform-independent tool. On Linux/Unix, JMeter can be invoked by clicking on JMeter shell script. On Windows it can be invoked by starting the jmeter.bat file.
• It has full Swing and lightweight component support (precompiled JAR uses packages javax.swing.* ).
• JMeter store its test plans in XML format. This means you can generate a test plan using a text editor.
• It's full multi-threading framework allows concurrent sampling by many threads and simultaneous sampling of different functions by separate thread groups.
• It is highly Extensible.
• Can also be used to perform automated and functional testing of your application.
Q: What is a Test Plan in JMeter?
A: A Test Plan defines and provides a layout of how and what to test. For example the web application as well as the client server application. It can be viewed as a container for running tests. A complete test plan will consist of one or more elements such as thread groups, logic controllers, sample-generating controllers, listeners, timers, assertions, and configuration elements. A test plan must have at least one thread group.
Q: List some of the test plan elements in JMeter.
A: Following is a list of some of the test plan elements:
• ThreadGroup
• Controllers
• Listeners
• Timers
• Assertions
• Configuration Elements
• Pre-Processor Elements
• Post-Processor Elements
Q: What is Thread Group?
A: Thread Group elements are the beginning points of your test plan. As the name suggests, the thread group elements control the number of threads JMeter will use during the test.
Q: What are Controllers and its types?
A: JMeter has two types of Controllers:
• Samplers Controllers : Samplers allow JMeter to send specific types of requests to a server. They simulate a user's request for a page from the target server. For example, you can add a HTTP Request sampler if you need to perform a POST, GET, DELETE on a HTTP service
• Logical Controllers : Logic Controllers let you control order of processing of Samplers in a Thread. Logic Controllers can change the order of request coming from any of their child elements. Some examples are: ForEach Controller, While Controller, Loop Controller, IF Controller, Run Time Controller, Interleave Controller, Throughput Controller, Run Once Controller.
Q: What is Configuration element?
A: Configuration Elements allow you to create defaults and variables to be used by Samplers. They are used to add or modify requests made by Samplers.
They are executed at the start of the scope of which they are part, before any Samplers that are located in the same scope. Therefore, a Configuration Element is accessed only from inside the branch where it is placed.
Q: What are Listeners?
A: Listeners let you view the results of Samplers in the form of tables, graphs, trees or simple text in some log files. They provide visual access to the data gathered by JMeter about the test cases as a Sampler component of JMeter is executed.
Listeners can be added anywhere in the test, including directly under the test plan. They will collect data only from elements at or below their level.
Q: What are Pre-Processor and Post-Processor elements?
A: A Pre-Procesor is something that will happen before a sampler executes. They are often used to modify the settings of a Sample Request just before it runs, or to update variables that are not extracted from response text.
A Post Processor executes after a sampler finishes its execution. This element is most often used to process the response data, for example, to retrieve particular value for later use.
Q: What is the execution order of Test Elements
A: Following is the execution order of the test plan elements:
1. Configuration elements
2. Pre-Processors
3. Timers
4. Sampler
5. Post-Processors (unless SampleResult is null)
6. Assertions (unless SampleResult is null)
7. Listeners (unless SampleResult is null)
Q: How do you ensure re-usability in your JMeter scripts?
A:
• Using config elements like "CSV Data Set Config", "User Defined Variables", etc for greater data reuse.
• Modularizing shared tasks and invoking them via a "Module Controller".
• Writing your own BeanShell functions, and reusing them.
Q: Are the test plans built using JMeter OS dependant?
A: Test plans are usually saved in thr XML format, hence they have nothing to do with any particular OS. You can run those test plans on any OS where JMeter can run.
Q: What are the monitor tests?
A: Uses of monitor tests are:
• Monitors are useful for a stress testing and system management.
• Used with stress testing, the monitor provides additional information about server performance.
• Monitors makes it easier to see the relationship between server performance and response time on the client side.
• As a system administration tool, the monitor provides an easy way to monitor multiple servers from one console.
Q: What are JMeter Functions?
A: JMeter functions are special values that can populate fields of any Sampler or other element in a test tree. A function call looks like this:
${__functionName(var1,var2,var3)}
Q: Where can functions and variables be used?
A: Functions and variables can be written into any field of any test component.
Q: What are regular expressions in JMeter?
A: Regular expressions are used to search and manipulate text, based on patterns. JMeter interprets forms of regular expressions or patterns being used throughout a JMeter test plan, by including the pattern matching software Apache Jakarta ORO.
Q: How can you reduce resource requirements in JMeter?
A: Below are some suggestion to reduce resource requirements:
• Use non-GUI mode: jmeter -n -t test.jmx -l test.jtl.
• Use as few Listeners as possible; if using the -l flag as above they can all be deleted or disabled.
• Disable the “View Result Tree” listener as it consumes a lot of memory and can result in the console freezing or JMeter running out of memory. It is, however, safe to use the “View Result Tree” listener with only “Errors” checked.
• Rather than using lots of similar samplers, use the same sampler in a loop, and use variables (CSV Data Set) to vary the sample. Or perhaps use the Access Log Sampler.
• Don't use functional mode.
• Use CSV output rather than XML.
• Only save the data that you need.
• Use as few Assertions as possible.
• Disable all JMeter graphs as they consume a lot of memory. You can view all of the real time graphs using the JTLs tab in your web interface.
• Do not forget to erase the local path from CSV Data Set Config if used.
• Clean the Files tab prior to every test run.

Testing objectives and purpose

What are software testing objectives and purpose?

Software Testing has different goals and objectives.The major objectives of Software testing are as follows:

■Finding defects which may get created by the programmer while developing the software.
■Gaining confidence in and providing information about the level of quality.
■To prevent defects.
■To make sure that the end result meets the business and user requirements.
■To ensure that it satisfies the BRS that is Business Requirement Specification and SRS that is System Requirement Specifications.
■To gain the confidence of the customers by providing them a quality product.

Software testing helps in finalizing the software application or product against business and user requirements. It is very important to have good test coverage in order to test the software application completely and make it sure that it’s performing well and as per the specifications.

While determining the coverage the test cases should be designed well with maximum possibilities of finding the errors or bugs. The test cases should be very effective. This objective can be measured by the number of defects reported per test cases. Higher the number of the defects reported the more effective are the test cases.

Once the delivery is made to the end users or the customers they should be able to operate it without any complaints. In order to make this happen the tester should know as how the customers are going to use this product and accordingly they should write down the test scenarios and design the test cases. This will help a lot in fulfilling all the customer’s requirements.

Software testing makes sure that the testing is being done properly and hence the system is ready for use. Good coverage means that the testing has been done to cover the various areas like functionality of the application, compatibility of the application with the OS, hardware and different types of browsers, performance testing to test the performance of the application and load testing to make sure that the system is reliable and should not crash or there should not be any blocking issues. It also determines that the application can be deployed easily to the machine and without any resistance. Hence the application is easy to install, learn and use.

Non-functional testing

What is Non-functional testing (Testing of software product characteristics)?

non-functional testing the quality characteristics of the component or system is tested. Non-functional refers to aspects of the software that may not be related to a specific function or user action such as scalability or security. Eg. How many people can log in at once? Non-functional testing is also performed at all levels like functional testing.

Non-functional testing includes:
■Functionality testing
■Reliability testing
■Usability testing
■Efficiency testing
■Maintainability testing
■Portability testing
■Baseline testing
■Compliance testing
■Documentation testing
■Endurance testing
■Load testing
■Performance testing
■Compatibility testing
■Security testing
■Scalability testing
■Volume testing
■Stress testing
■Recovery testing
■Internationalization testing and Localization testing

■Functionality testing: Functionality testing is performed to verify that a software application performs and functions correctly according to design specifications. During functionality testing we check the core application functions, text input, menu functions and installation and setup on localized machines, etc.
■Reliability testing: Reliability Testing is about exercising an application so that failures are discovered and removed before the system is deployed. The purpose of reliability testing is to determine product reliability, and to determine whether the software meets the customer’s reliability requirements.
■Usability testing: In usability testing basically the testers tests the ease with which the user interfaces can be used. It tests that whether the application or the product built is user-friendly or not.

Usability testing includes the following five components:
■Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?
■Efficiency: How fast can experienced users accomplish tasks?
■Memorability: When users return to the design after a period of not using it, does the user remember enough to use it effectively the next time, or does the user have to start over again learning everything?
■Errors: How many errors do users make, how severe are these errors and how easily can they recover from the errors?
■Satisfaction: How much does the user like using the system?
■Efficiency testing: Efficiency testing test the amount of code and testing resources required by a program to perform a particular function. Software Test Efficiency is number of test cases executed divided by unit of time (generally per hour).
■Maintainability testing: It basically defines that how easy it is to maintain the system. This means that how easy it is to analyze, change and test the application or product.
■Portability testing: It refers to the process of testing the ease with which a computer software component or application can be moved from one environment to another, e.g. moving of any application from Windows 2000 to Windows XP. This is usually measured in terms of the maximum amount of effort permitted. Results are measured in terms of the time required to move the software and complete the and documentation updates.
■Baseline testing: It refers to the validation of documents and specifications on which test cases would be designed. The requirement specification validation is baseline testing.
■Compliance testing: It is related with the IT standards followed by the company and it is the testing done to find the deviations from the company prescribed standards.
■Documentation testing: As per the IEEE Documentation describing plans for, or results of, the testing of a system or component, Types include test case specification, test incident report, test log, test plan, test procedure, test report. Hence the testing of all the above mentioned documents is known as documentation testing.
■Endurance testing: Endurance testing involves testing a system with a significant load extended over a significant period of time, to discover how the system behaves under sustained use. For example, in software testing, a system may behave exactly as expected when tested for 1 hour but when the same system is tested for 3 hours, problems such as memory leaks cause the system to fail or behave randomly.
■Load testing: A load test is usually conducted to understand the behavior of the application under a specific expected load. Load testing is performed to determine a system’s behavior under both normal and at peak conditions. It helps to identify the maximum operating capacity of an application as well as any bottlenecks and determine which element is causing degradation. E.g. If the number of users are in creased then how much CPU, memory will be consumed, what is the network and bandwidth response time
■Performance testing: Performance testing is testing that is performed, to determine how fast some aspect of a system performs under a particular workload. It can serve different purposes like it can demonstrate that the system meets performance criteria. It can compare two systems to find which performs better. Or it can measure what part of the system or workload causes the system to perform badly.
■Compatibility testing: Compatibility testing is basically the testing of the application or the product built with the computing environment. It tests whether the application or the software product built is compatible with the hardware, operating system, database or other system software or not.
■Security testing: Security testing is basically to check that whether the application or the product is secured or not. Can anyone came tomorrow and hack the system or login the application without any authorization. It is a process to determine that an information system protects data and maintains functionality as intended.
■Scalability testing: It is the testing of a software application for measuring its capability to scale up in terms of any of its non-functional capability like load supported, the number of transactions, the data volume etc.
■Volume testing: Volume testing refers to testing a software application or the product with a certain amount of data. E.g., if we want to volume test our application with a specific database size, we need to expand our database to that size and then test the application’s performance on it.
■Stress testing: It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. It is a form of testing that is used to determine the stability of a given system. It put greater emphasis on robustness, availability, and error handling under a heavy load, rather than on what would be considered correct behavior under normal circumstances. The goals of such tests may be to ensure the software does not crash in conditions of insufficient computational resources (such as memory or disk space).
■Recovery testing: Recovery testing is done in order to check how fast and better the application can recover after it has gone through any type of crash or hardware failure etc. Recovery testing is the forced failure of the software in a variety of ways to verify that recovery is properly performed. For example, when an application is receiving data from a network, unplug the connecting cable. After some time, plug the cable back in and analyze the application’s ability to continue receiving data from the point at which the network connection got disappeared. Restart the system while a browser has a definite number of sessions and check whether the browser is able to recover all of them or not.
■Internationalization testing and Localization testing: Internationalization is a process of designing a software application so that it can be adapted to various languages and regions without any changes. Whereas Localization is a process of adapting internationalized software for a specific region or language by adding local specific components and translating text.

Manual Testing

What is Manual Testing?

Manual Testing is a process carried out to find the defects. In this method the tester plays an important role as end user and verify all features of the application to ensure that the behavior of the application. The Manual Testing is very basic type of testing which helps to find the bugs in the application under test. It is preliminary testing, must be carried out prior to start automating the test cases and also needs to check the feasibility of automation testing. The Test Plan is created & followed by the tester to ensure that the comprehensiveness of testing while executing the test cases manually without using automation testing tool.

It is not necessary to have knowledge of any testing tool for manual software testing. As the Software testing fundamental always says that “100% Automation is not possible” so the Manual Testing is very important.

Goal of Manual Testing

The main Goal of Manual Testing is to make sure that the application under test is defect free and software application is working as per the requirement specification document.

This type includes the testing of the Software manually i.e. without using any automated tool or any script. In this type, tester takes over the role of end user and test the Software to identify any un-expected behavior or bug. There are different stages for Manual Testing like Unit testing, Integration testing, System testing and User Acceptance testing.

A test plan document is created by test lead which describes the detailed and systematic approach to testing a software application. Basically the test plan typically includes a complete understanding of what the ultimate workflow will be. To ensure the completeness of testing (100% test coverage) test cases or test scenarios are created. Manual Testing Concepts also includes exploratory testing as testers explore the software to identify errors in it

After the testing is started the designed test cases or test scenarios will be executed & any differences between actual & expected results are reported as defects. Once the reported defects are fixed, the testers will retest the defect to make sure that the defects are fixed. The main goal of Software testing is to make software defect free & deliver good quality Product to customer.

Manual Testing types:

Here are different Manual testing types; these types of testing can be carried out manually as well as using automation tool.

Difference Between Manual Testing and Automation Testing

Manual testing will be used when the test case only needs to runs once or twice.
Automation testing will be used when need to execute the set of test cases tests repeatedly.
Manual testing will be very useful while executing test cases first time & may or may not be powerful to catch the regression defects under frequently changing requirements.
Automation testing will be very useful to catch regressions in a timely manner when the code is frequently changes.
Manual testing is less reliable while executing test cases every time. Using manual software testing it may not be perform test cases execution with same precision.
Automation tests will help to perform same operation precisely each time. Simultaneously testing on different machine with different OS platform combination is not possible using manual testing. To execute such task separate testers are required.
Automation testing will be carried out simultaneously on different machine with different OS platform combination. To execute the test cases every time tester required same amount of time. Once Automation test suites are ready then less testers are required to execute the test cases. No programming can be done to write sophisticated tests which fetch hidden information. Using Automation testing, Testers can program complicated tests to bring out of sight information.
Manual testing is slower than automation. Running tests manually can be very time consuming. Automation runs test cases significantly faster than human resources.
Manual testing requires less cost than automating it. Initial cost to automate is more than manual testing but can be used repetitively. It is preferable to execute UI test cases using manual testing. Sometimes can’t automate the UI test cases using automation testing. To execute the Build Verification Testing (BVT) is very mundane and tiresome in Manual testing.
Automation testing is very useful for automating the Build Verification Testing (BVT)
Manual testing will be used when the test case only needs to runs once or twice.
Automation testing will be used when need to execute the set of test cases tests repeatedly.
Manual testing will be very useful while executing test cases first time & may or may not be powerful to catch the regression defects under frequently changing requirements.
Automation testing will be very useful to catch regressions in a timely manner when the code is frequently changes.
Manual testing is less reliable while executing test cases every time. Using manual software testing it may not be perform test cases execution with same precision.
Automation tests will help to perform same operation precisely each time.
Simultaneously testing on different machine with different OS platform combination is not possible using manual testing. To execute such task separate testers are required.
Automation testing will be carried out simultaneously on different machine with different OS platform combination.
To execute the test cases every time tester required same amount of time.
Once Automation test suites are ready then less testers are required to execute the test cases.
No programming can be done to write sophisticated tests which fetch hidden information.
Using Automation testing, Testers can program complicated tests to bring out of sight information.
Manual testing is slower than automation. Running tests manually can be very time consuming.
Automation runs test cases significantly faster than human resources.
Manual testing requires less cost than automating it.
Initial cost to automate is more than manual testing but can be used repetitively.
It is preferable to execute UI test cases using manual testing.
Sometimes can’t automate the UI test cases using automation testing.
To execute the Build Verification Testing (BVT) is very mundane and tiresome in Manual testing.
Automation testing is very useful for automating the Build Verification Testing (BVT).

Testing Q &A

MANUAL TESTING QUESTIONS & ANSWERS
1. What is meant by Priority and severity?
Severity:
1. This is assigned by the Test Engineer
2. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release.
Priority:
1. This is assigned by the Developer.
2. This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement.
Egg. The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions:
a> It is not accepting any value
b> It is accepting value but output is in non-defined format (say Unicode Characters).
A good example I used some Unicode characters to generate a left defined arrow, it displayed correctly but after saving changes it gave some address value from the
Stack of this server. For more information mail me I will let you know.
2. Give me some example for high severity and low priority defect?
If suppose the title of the particular concern is not spelled correctly, it would give a negative impacted ICICC is spelled as a title for the project of the concern ICICI. Then it is a high severity, low priority defect.
3. What is basis for test case review?
The main basis for the test case review is
1. Testing techniques oriented review
2. Requirements oriented review
3. Defects oriented review.
4. What are the contents of SRS documents?
Software requirements specifications and Functional requirements specifications.
5. What is difference between the Web application testing and Client Server testing?
Testing the application in intranet (without browser) is an example for client -server. (The company firewalls for the server are not open to outside world. Outside people cannot access the application.)So there will be limited number of people using that application.
Testing an application in internet (using browser) is called web testing. The application which is accessible by numerous numbers around the world (World Wide Web.)
So testing web application, apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is an e-commerce testing application we go for Usability etc… Testing.
6. Explain your web application architecture?
Web application is tested in 3 phases
1. Web tier testing –> browser compatibility
2. Middle tier testing –> functionality, security
3. Data base tier testing –> database integrity, contents
7.suppose the product/application has to deliver to client at 5.00PM,At that time you or your team member caught a high severity defect at 3PM.(Remember defect is high severity)But the client is cannot wait for long time. You should deliver the product at 5.00Pm exactly. Then what is the procedure you follow?
The bug is high severity only so we send the application to the client and find out the severity is priority or not. If its priority then we ask him to wait.
Here we found defects/bugs in the last minute of the delivery or release date
Then we have two options
1. Explain the situation to client and ask some more time to fix the bug.
2. If the client is not ready to give some time then analyze the impact of defect/bug and try to find workarounds for the defect and mention these issues in the release notes as known issues or known limitations or known bugs. Here the workaround means remedy process to be followed to overcome the defect effect.
3. Normally this known issues or known limitations (defects) will be fixed in next version or next release of the software
8. Give me examples for high priority and low severity defects?
Suppose in one banking application there is one module ATM Facility. In that ATM facility when ever we are depositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing
Of message. In this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be
Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects…
9. Explain about Bug life cycle?
1) Tester->
2) Open defect->
3) Send to developer
4) ->if accepted moves to step5 else sends the bug to tester gain
5) Fixed by developer ->
6) Regression testing->
7) No problem inbuilt and sign off
->if problem in built reopen the issue send to step3
10. How can you report the defect using excel sheet?
To report the defect using excel sheet
Mention: The Future that been effected.
Mention: Test Case ID (Which fail you can even mention any other which are dependency on this bug)
Mention : Actual Behavior
Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section
Mention : Your Test Setup used during Testing
Mention : Steps to Re-Produce the bug
Mention : Additional Info
Mention : Attach a Screen Shot if it is a GUI bug
Mention : Which other features it is blocking because of this bug that you are unable to
Execute the test cases.
Mention: How much time you took to execute that test case or follow that specific TC
Which leaded to bug?
11.If you have executed 100 test cases ,every test case passed but apart from these test case you found some defect for which test case is not prepared,thwn how you can report the bug?
While reporting this bug into bug tracking tool you will generate the test case mean put the steps to reproduce the bug.
12. What is the difference between web based application and client server application?
The basic difference between web based application & client server application is that the web application are 3 tier & client based are 2 trier.In web based changes are made at one place & it is reflected on other layers also whereas client based separate changes need be installed on client machine also.
13. What is test plan? And can you tell the test plan contents?
Test plan is a high level document which explains the test strategy, time lines and available resources in detail. Typically a test plan contains:
-Objective
-Test strategy
-Resources
-Entry criteria
-Exit criteria
-Use cases/Test cases
-Tasks
-Features to be tested and not tested
-Risks/Assumptions.
14. How many test cases can you write per a day, an average figure?
Complex test cases 4-7 per day
Medium test cases 10-15 per day
Normal test cases 20-30 per day
15. Who will prepare FRS (functional requirement documents)? What is the important of FRS?
The Business Analyst will pre pare the FRS.
Based on this we are going to prepare test cases.
It contains
1. Over view of the project
2. Page elements of the Application (Filed Names)
3. Prototype of the of the application
4. Business rules and Error States
5. Data Flow diagrams
6. Use cases contains Actor and Actions and System Responses
16. How you can decide the number of test cases is enough for testing the given module?
The developed test cases are covered all the functionality of the application we can say test cases are enough. If u knows the functionality covered or not u can use RTM.
17. What is the difference between Retesting and Data Driven Testing?
Retesting: it is manual process in which application will be tested with entire new set of data.
Data Driven Testing(DDT)-It is a Automated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring
Procedure.
18. What is regression testing?
After the Bug fixed, testing the application whether the fixed bug is affecting remaining functionality of the application or not.Majorly in regression testing Bug fixed module and it’s
Connected modules are checked for their integrity after bug fixation.
19. How does u test web application?
Web application testing
Web application should have the following features like
1. Attractive User Interface (logos, fonts, alignment)
2. High Usability options
3. Security features (if it has login feature)
4. Database (back end).
5. Performance (appearing speed of the application on client system)
6. Able to work on different Browsers (Browser compatibility), O.S compatibility (technically called as portability)
7. Broken link testing………etc
so we need to follow out the following test strategy.
1. Functionality Testing
2. Performance Testing (Load, volume, Stress, Scalability)
3. Usability Testing
4. User Interface Testing (colors, fonts, alignments…)
5. Security Testing
6. Browser compatibility Testing (different versions and different browser)
7. Broken link and Navigation Testing
8. Database (back end) Testing (data integrity)
9. Portability testing (Multi O.s Support)….etc
20. How does u perform regression testing, means what test cases u select for regression?
Regression testing will be conducted after any bug fixed or any functionality changed.
During defect fixing procedure some part of coding may be changed or functionality may be manipulated. In this case the old test cases will be updated or completely re written
According to new features of the application where bug fixed area. Here possible areas are old test cases will be executed as usual or some new test cases will be added to existing test cases or some test cases may be deleted.
21. What r the client side scripting languages and server side scripting languages?
Client side scripting languages are
Javascript, VbScript, PHP…etc
Server side Scripting languages are
Perl, JSP, ASP, PHP.etc
Client side scripting languages are useful to validate the inputs or user actions from user side or client side.
Server side Scripting languages are to validate the inputs at server side.
These scripting languages provide security for the application. And also provides dynamic nature to web or client server application
Client side scripting is good because it won’t send the unwanted input’s to server for validation. From front-end it self it validated the user inputs and restricts the user activities and guides him
22. If a very low defect (user interface) is detected by u and the developer not compromising with that defect,what will u do?
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1. Reproduce the defect
2. Capture the defect screen shots
3. Document the proper inputs that you are used to get the defect in the defect report
3. Send the defect report with screen shots, i/ps and procedure for defect reproduction.
Before going to this you must check your computer hard ware configuration that is same as developer system configuration. And also check the system graphic drivers are properly
Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the above method.
23.if u r only person in the office and client asked u for some changes and u didn’t get what the client asked for what will u do?
One thing here is very important. Nobody will ask test engineer to change software that is
not your duty, even if it is related to testing and anybody is not there try to listen care fully if you are not understand ask him again and inform to the corresponding people immediately.
Here the client need speedy service, we (our company) should not get any blame from customer side.
24. How to get top two salaries from employee tables?
Select * from EMP e where 2>= (select count (*) from EMP e where sal>e.sal) order by desc sal.
25. How many Test-Cases can be written for the calculator having 0-9 buttons, Add, Equalto buttons? The test cases should be focused only on add-functionality but mot GUI.What is those test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press ‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’ labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions will not vary so first number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways in the same way second number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
Total number of possibilities are =10×10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending.
then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test cases are enough to test the calculator functionality.
26. What is positive and negative testing.Explain with example?
Positive Testing - testing the system by giving the valid data.
Negative Testing - testing the system by giving the Invalid data.
For Exam application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.
27. How will you prepare Test plan. What are the techniques involved in preparing the Test plan?
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are resolved.
Project milestones: dead lines
28. What is the Defect Life Cycle?
Defect life cycle is also called as bug life cycle. It has 6stages namely
1. New: found new bug
2. Assigned: bud assigned to developer
3. Open: developer is fixing the bug
4. Fixed: developer has fixed the bug
5. Retest: tester retests the application
6. closed/reopened: if it is ok tester gives closed statuselse he reopens and sends back to developer.
29. Expalin about metrics Management?
Metrics: is nothing but a measurement analysis.Measurment analysis and Improvement is one of the process area in CMM I L2.
30. What is performance Testing and Regression Testing?
Performance Testing:-testing the present working condition of the product
Regression Testing:-Regression Testing is checking for the newly added functionality causing any errors interims of functionality and the common functionality should be stable
In the latest and the previous versions
31.How do you review test case? Type of Review…
Types of reviewing test cases depend upon company standards, viz..,
Peer review, team lead review, project manager review.
Some times client may also review the test cases reg what is approach following for project
32. In which way tester get Build A, Build B, Build Z of an application, just explains the process?
After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive
The build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.
In case of Client server, the build is placed in the VSS (Configuration tool) which will help you get the .exe downloaded to your computer.
33. Apart from bug reporting what is your involvement in project life cycle?
As a Test engineer we design test cases, prepare test cases Execute Test cases, track the bugs, analyze the results report the bugs. Involved in regression testing, performance of system
Testing system integration testing at last preparation of Test summary Report

34.What are the contents of test report?
There are two documents, which should be prepared at particular phase.
1. Test Results document.
2. Test Report document.
Test Results doc will be prepared at the phase of each type of Testing like FULL FUNCTIONAL TEST PASS,REGRESSION TEST PASS,SANITY TEST PASS etc…Test case execution against
The application. Once you prepared this doc, we will send the doc to our TL and PM.By seeing the Test Results doc, TL will come to know the coverage part of the testcase.Here I am giving you the contents used in the Test Results doc?
1. Build No
2. Version Name
3. Client OS
4. Feature set
5. Main Feature
6. Defined Test cases on each feature.
7. QA engineer Name
8. Test e-cases executed. (Includes pass and fail)
9. Testcases on HOLD (Includes blocking test cases and deferred Test cases)
10. Covereage Report (Which includes the coverage ratings in %, like % of test cases covered, % of test cases failed)
Coming to Test report, generally we will prepare Test report, once we rolled out the product to our client. This document will be prepared by TL and delivered to the client.Mainly, this document describes the what we have done in the project, chievements we have reached, our
Learning’s in throughout the project etc…The other name for Test report is Project Closure Report and we will summarize the all the activities, which have taken place in through out the project. Here I am giving your the contents covered in the Test Report.
1. Test Environment (Should be covered the OS, Application or webservers, Mahchine names, Database, etc…)
2.Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform Testing, regression Testing,etc..
3. Major areas Covered.
4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)
5. Work schedule (When we start the testing and we finished)
6. Defect Analysis
6.1 Defects logged in different types of tests like Functional Test, regressiion Test as per area wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysis for the bugs marked as NOT A BUG.
7. QA observations or learning’s thought the life cycle.
35. Write high level test cases?
Write all the test cases under high level TC, which can be covered the main functionalities like
Creation, edition, deletion, etc….as per prescribed in the screen.
Write all the test cases under low level TC,which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.
Example a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC
And low level test cases.
HIGH LEVEL TC
1. Verify that User is able to login with valid login and valid password.
2. Verify that User is not able to login with invalid login and valid password.
Etc…
3. Verify that Reset button clears the filled screen.
4. Verify that a pop up message is displayed for blank login.
LOW LEVEL TC
1. Verify that after launching the URL of the application below fields are displays in the screen.
1. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.
5. Check box, provided for the label “remember my pwd” is unchecked.
2. Verify that OK button should be disabled before selecting login and password fields.
3. Verify that OK button should we enabled after selecting login and password.
4. Verify that User is able to check the check box, providedfor the label “remember my password”.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
36. What is test scenario?
Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.
Please see the below example, which is exactly matched to my explanation.
As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.
Scenario: USER’S LOGIN
Conditions to be checked to test the above scenario:
—————————————————-
1. Test login field and Password fields individually.
2. Try to login with valid login and valid password.
3. Try to login with invalid login and valid password. Etc
37. What is build duration?
it is a tine gap between old version build and new version build in new version build some new extra features are added
38. What is test deliverables?
Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template Test deliverables will be delivered to the client not only for the completed activities, but also for the activites, which we are implementing for the better productivity. (As per the company’s standards).Here I am giving you some of the Test deliverables in my project.
1. QA Test Plan
2. Test case Docs
3. QA Test plan, if we are using Automation.
4. Automation scripts
5. QA Coverage Matrix and defect matrix.
6. Traceability Matrix
7. Test Results doc
8. QA Schedule doc (describes the deadlines)
9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)
10. Weekly status report (sent by PM to the client)
11. Release Notes.
39. What is your involvement in test plan?
Test lead is involved in preparing test plan test engineers are no way related in preparing test plan role TE is test case design, and execution and bug tracking and reporting them Generally TL is involved in preparation of the TestPlan.But it is not mandatory only TL will take main part in the preparation of the TP.Test engineer can suggest to TL, if he (or) she has good understanding on project and resources, if he or she has more exp with the project, if TL is wrongly given deadlines. If your suggestions are valid, TL will incorporate all of them to the TestPlan.But in most of the companies Test engineers are just audience.
40. Which test cases are not to be automated?
All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance
41. If a project is long term project, requirements are also changes then test plan will change or not? Why?
Yes. Definitely. If requirement changes, the design documents, specifications (for that particular module which implements the requirements) will also change. Hence the test plan would also need to be updated. This is because “Resource Allocation” is one section in the test
Plan. We would need to write new test cases, review, and execute it. Hence resource allocation would have to be done accordingly. As a result the Test plan would change
42. Explain VSS (Virtual Source Safe)?
After completion of all phages from development side developer store the code in development folder of VSS, Testing team copying code from that folder to testing folder, after completing above phages from testing, testers put the build in base line folder. It is version control Tool
Mainly useful to developer, to storing code and maintains version Copying a code from VSS By developer is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.
43. Who will assign severity & priority?
The tester/developer should give the priority based on severity of the bug
Severity means: is the impact of the bug on the application .i.e seriousness of the bug interims of the functionality.
Priority means: is how soon it should get fixed i.e. importance of the bug interims of customer
44. What is the Difference between Stub Testing and Driver Testing?
Stub testing:
In top down approach, a core module is developed. To test that core module, small dummy modules r used. So stubs r small dummy modules that test the core module.
Driver testing:
In bottom up approach, small modules r developed. To test them a dummy core module called driver is developed.
45. What is a “Good Tester”?
Is one who tries to break the developers software and in a position to venture the bugs. So that at least 80% bugs free software can deliver.
46. What is cookie And Session testing?
A small text file of information that certain Web sites attach to a user’s hard drive while the user is browsing the Web site. A Cookie can contain information such as user ID, user preferences, archive shopping cart information, etc. Cookies can contain Personally Identifiable
Information. Session is a connection between a server and client.
47. How would you perform testing manually for web site?
By noting the time to load page or perform any action with stop watch. I know it sounds funny but this is the way performance is tested manualy.
48. What is use case? Tell me the attribute of use case?
“Use Case is description of functionality certain features of an application interims of Actors, actions and responsibilities.”
Use Case attributes are:
1. Information of Document, 2. Description, 3. Objective, 4. Actors, 5.Pre-conditions, 6.Data-element descriptions, 7.post conditions, 8.primary flow, 9. Alternative flow and Business rules/interaction implementations and etc….
49. What is the difference between stress, volume and load testing?
Load Testing gradually increase the load and check the performance of the application .v check at what point or maximum load application can sustain.
Stress testing: In this testing v check the performance of application under extreme condign which rarely occurs like
(1)Many concurrent user access the application for short time.
(2) Extra ordinary long transaction.
(3) Very short transaction reputed quickly.
50. When will do the beta test? When will do the alpha test?
Alpha and Beta tests comes under User acceptance test. We will conduct these two systems being released. We are giving opportunity to customer to check all punctualities covered or not.
Alpha testing conducting for software application by real customer at development site.
Beta testing conducting for software product by model customer at customer site.
52. How do you select test cases for Regression Testing (The point is when there is change code how do you come to know which part of code or modules it will affect)?
Consider an example of a form which has a user name, password and Login button.
There is a code change and a new button “Reset” is introduced. Regression testing (for that build) will include testing only the “Login” button and not the Reset button (testing Reset button will be a part of conation testing). Hence the Regression tester need not worry about the change in code, functionality. But he has to make sure that the existing functionality is working as desired. Testing of “Reset” button will be included as a part of Regression, for the next build
53. Can you explain with example of high seviority and low priority, low seviority and high priority, high seviority and high priority, low seviority and low priority?
1. High severity and high priority - Database connectivity cannot be established by multiple users.
2. Low severity and low priority - Small issues like, incorrect number of decimal digits in the output.
3. Low severity and high priority - Images not updated.
4. High severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.
(1)High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
(2) Low priority & low severity: In login window, spell of ok button is “Ko”.
(3)Low priority & high serverty: In login window, there is a restriction login name should be 8 characters if user enter 9 or than 9 in that case system get crash.
(4)High priority & low severity: Suppose logo of any brand company is not proper in their product. So it affects their business.
54. What will be the Test case for ATM Machine & Coffee Machine?
Test cases for ATM Machine
1. Successful inspection of ATM card
2. Un successful operation due to insert card in wrong angle
3. Un successful operation due to invalid account ex: other bank card or time expired card
4. Successful entry of PIN number
5. Un successful operation due to enter wrong PIN number 3times
6. Successful selection of language
7. Successful selection of account type
8. Un successful operation due to invalid account type
10. Successful selection of withdraw operation
11. Successful selection of amount to be withdraw
12. Successful withdraw operation
13. Unsuccessful withdraw operation due to wrong denominations
14. Unsuccessful withdraw operation due to amount is greater than day limit
15. Unsuccessful withdraw operation due to lack of money in ATM
16. Unsuccessful withdraw operation due to amount is greater than possible balance
17. Unsuccessful withdraw operation due to transactions is greater than day limit
18. Unsuccessful withdraw operation due to click cancel after insert card
19. Unsuccessful withdraw operation due to click cancel after insert card & pin number
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
21. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language &account type
22. Unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type & withdraw operation
23.unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type ,withdraw operation &amount to be withdraw
55. Tell me about your daily activities as a test engineer?
Role:
1. Understanding the BRS and Use cases Document
2. Giving system demo to PM, System analyst, designer, Dev lead.
3. Preparing the Test Actions in xls sheet.
4. Updating the Test Actions based on review comments by System analyst/Business Analyst.
5. Preparing the Test cases and Datasets (System level and global level datasets) in word document
6. Updating the Test Cases based on review comments by System analyst.
7. Installing the application-Testing environment set up.
8. Performing Functional, GUI, System, Compatibility testing (If necessary), Regression testing based on Test cases
9. Preparing the defect report, Bug tracking list and sending daily status report to PM, leads.
56. In SDLC process what is the role of PM, TL, DEVELOPER, tester in each and every phase? Please explain me in detail?
In the SDLC we have these phases
1. Initial phase
2. Analysis phase
3. Designing phase
4. Coding phase
5. Testing
6. Delivery and maintenance
In the initial phase project manager can prepare a document for the requirements, team leader will prepare a team which is having test engineers, developer will provided by the project manager, tested will prepare test cases for that particular project
Analysis phase all the members have a meeting to finalize the technology to develop that project, the employee, time…
Designing phase the project manager like senior level management will give the directions and source code to the team members to develop the actual code that is guidelines will be given in this phase
Coding phase developer will develop the actual code using the source code and they release the application to the tested
Testing phase they deploy their test cases to that application and prepare a bug profile document if there is any defect/bug in that application and send it back to developer, developer may rectify and releases than application as next build and if the bug not understand it will send to the project lead in the delivery phase the so test eng can deploy the application in the client environment
Maintenance phase if the client get any problem with the application it may solved by the project lead with help of testers and developers.
57. How do you Test Application with having any requirement and Document?
If it is an existing system or if a build is available then we explore the system while testing. This helps knowing the functional use of the system, and its usability.
By asking questions to end users and how they use it will be more beneficial. Also, you may work with BA to know more about the system.
Black box test is nothing but the same where you explore the system without having any prior knowledge to the system.
58. What is back end testing using SQL?
Executing SQL statements to check if the data submitted by a GUI program is updated in the database or not? Executing the statement the data base is connecting to that particular changes, updations or not it will test. Back end testing is the testing the integration between the application and the database. It is checking the changes made in the database are getting reflected in the application.
Example: A new column is added in the table. Here we test by giving values in the application and value has to be stored in the table.
59. What are the reasons why parameterization is necessary when load testing the Web server and the database server?
When you test your applications, you may want to check how the application performs the same operations with multiple sets of data. For example, suppose you want to check how
Your Web site responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create Data Table parameters so that your test runs ten times, each time using a different set of data.
60. Difference between strategic test plan & test plan?
Strategic test is an organizational level term which is applied for all the projects in the organization with small customizations
Test plan is project level term and which can be applied for that specific project only.
Test plan is a strategic document which describes how to perform testing in an efficient effective and uptimes way. Quality lead test lead can prepare this test plan
Strategic test plan is an already or new test plan which can bow used in the future for another project also with some changes in the same organisation.
61. Draw Backs of automated testing?
DRAW BACKS OF AUTMATION
Expensive, lack of expertisation, all the areas we can not automate
62. When will u make update and modify the test object properties in the repository?
When ever the developer may change any one of the object properties definitely we have to change the same in the OR object repository. If new version net build released from the development department we the test engineers must to modify or update the same is compulsory, other wise than test will show the bug
63. What is the document needed to create a test case? How u tell it is test case?
System requirements specification, Use case document, Test Plan
64. In customer details form having fields like customer name, customer address. After completion of this module, client raise the change as insert the two radio buttons after customer address. How you can check as a tester?
1. First we need to verify whether the radio button is there are not?
2. Conform the radio buttons are present after the customer address or not.
3. Verify the no of radio button.
4. Verify only one radio button should be checked initially when we open the Customer details form (if it is mentioned in FS)
5. Verify the functionality of the radio buttons i.e. if we check one ratio button, second radio button should be unchecked.
6. Verify the spell check of radio button label name.
7. Verify the alignment of radio buttons in the form.

65. At the time of testing web based applications and client server applications, what you absorbed as a tester?
We generally check for the links, data retrieving and posting.
We perform load and stress testing especially for Web based and Client-Server applications.
66. What are the documents required to prepare test plan?
Introduction, scope, test team and their responsibilities, test environment S/W & H/W requirements, test data preparation, levels of testing, seviority & priority, schedule, risk, automation Plan, features to test, bug life cycle all these are documents of test plan.
67. What is testing policy and testing methodology? And what is the difference?
Testing policy means all types of testing or testing techniques (i.e. functional testing, sanity testing etc).Testing methodology means white box and black box testing.
68. What is comparison testing?
Comparison Testing means comparing your software with the better one or you’re Competitor.
While comparison Testing we basically compare the Performance of the software. For ex If you have to do Comparison Testing of PDF converter(Desktop Based Application) then you will compare your software with your Competitor on the basis of:-
1. Speed of Conversion PDF file into Word.
2. Quality of converted file.
69. What is the general testing process?
Testing Process:
1. Test requirements analysis
2. Creation of Test Strategy (Which includes creation of Test Cases)
3. Creation of Test Plans (Which includes Test Cases and Test Procedures)
4. Execution of test cases
5. Analyze the test results
6. Report the defects if any
70. What participation a manual tester can do in documentation? Are there any tools available for only documentation?
Yes, Manual tester will do Sub Test plan documents, as of my knowledge no tool is used to prepare documentation
71. What is the difference between low and high level test cases? Give Examples?
High level Test cases are those which covers major functionality in the application (i.e. retrieve, update display, cancel (functionality related test cases), database test cases).
Low level test cases are those which are related to UI related testcases.
72. Is it mandatory to use USECASES or directly one can write test cases from requirements?
It’s not mandatory to write Use Cases, if the requirements are clear you can go ahead with Test Cases. Use Cases are written to know the business flow of the module/application.
73. How does u develop test harness?
Test Environment Test Bed
Test Environment S/W and H/W
Test Bed: Test Documents like Test Plan Document, Test Case Document.
Test Environment means
• Test Bed installation and configuration
• Network connectivity’s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others
74. Given requirement collection doc, tester can prepare which test plan?
Test lead can prepare a test plan which performs testing on an application in an efficient effective and in an optimized way. Test development will done by the testers using the test
Plan in the test plan they prepare the test strategy.
75. Tester with develop meant knowledge will be more effective .justify?
If tester has experience in Development, it will be useful when testing for logical thinking where the error occurs, what is the cause? He can guess the functionality of component? He can easily understand the application environment? Those are plus points which people have
Development experience.
Precisely he can justify that either functionality is wrong or right and can analyze the defects
76.As far as the SDLC is concerned last test case,will it be written for “Maintenance Phase”?
As far as the SDLC is concerned last test case will be written for “Acceptance Testing”
77. What is test scenario and test case? Please explain in detail?
Test Scenario:
Test scenario is like laying out plans for testing the product, environmental condition, number of team members required, making test plans, making test cases and what all features are to be tested for the product. Test scenario is very much dependent on the product to be tested.
Test scenario is made before the actual testing starts.
Test Case:
Test case is a document which provides the steps to be executed which has been planned earlier. It also depends on the type of product to be tested. Number of test cases is
Not fixed for any product.
78. What is the difference between Project Based Testing and Product Based Testing?
Project based is nothing but client requirements. Product based is nothing but market requirements. Ex.stiching shirt is a project based and ready made shirt is product based.
80. What is testing process in related to Application testing process is the one which tells you how the application should be tested in order to minimize the bugs in the application?
One main thing no application can be released as bug free application which is impossible.
81. What is the difference b/n Testing Methodology and Testing methods?
Testing Methodology define process, set of rules and principle which are follow by group concerned with testing the application. Here I explain 7 step testing methodology:
1. Test Requirement Analysis
2. Test Plan
3. Test Design
4. Test execute
5. Defect track
6. Test Automation
7. Test Maintain
Testing methods or we can say that Testing Techniques:
White Box Testing (Unit Testing, Integration Testing)
Black Box Testing (System Testing, Functional Testing, Performance Testing>Load testing>stress testing>volume testing & Security Testing) UAT (done by user/client with actual/live data)
82. What are starting links to test while website testing?
Web based systems are those using the internet, intranet and extranets Web based testing only needs be done once for any applications using the web. Web based testing are as follows:
1. Functional correctness
2. Integration
3. Usability
4. Security
5. Performance
6. Verification of code
83. How GUI testing will be done in manual testing for a website?
For any testing there should be some set of standards to be followed. Particularly in GUI testing, look and feel should be good. We should follow the requirements specification documents for GUI testing.
There should be some screen shots (given by client) which we should follow as it is.
And for button sizes, font, font size ,colors used, placing of links, objects and the placing of the objects in the page should be followed some standards. If we take a button in the page that should be some standard size. If the size of that button is more or less the client feel bad about that. So we should have minimum common since while testing GUI testing. Some time there may be some mistakes in the screen shots provided by the client also, but that is our responsibility to raise those issues.
84. What things should be tested in regression testing?
While doing Regression Testing a tester must check that any new updating or Modification or Change in Functionality of a Particular Component or Module does not create any disorder and any negative affects on the functionality of the Application
85. What is the document required to prepare during testing?
Normally Test engineers are responsible for any release of a project. Even the release is for staging environment or change request release or production release
The minimum documents are
1. Test Plan
2. Test Cases
3. Test Case Report
4. Bug report.
5. Release notes (which contains known issues).
6. Installation document.
86. What is Test data? Where we are using this in testing process?
What is the importance of this data?
To execute test cases we should have test data. This test data should be for positive and negative testings.for win runner we can get this test data from keyboard, excel sheets or from data base
87. What is the difference between test case and test script?
Test case is a description what data to be tested and what data to be inserted what are the actions to be done to check actual result against expected result what are the actual inputs we will use? What are the expected results? Is called test script
Test 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.
89. What is the difference between bug, error and defect?
At the time of coding mistake error, when the mistake noticed by the tester defect, tester sends this defect to development team if the developer agrees then it is bug
90. What is the difference between quality assurance and system testing explains in detail with an example?
Quality Assurance: It is nothing but building an adequate confidence in the customer that the developed software is acceding to requirements. Entire SDLC comes under QA. It is process oriented.
System Testing: It is the process of executing entire system i.e. checking the s/w as well as parts of system.

91. 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.
92. What is the difference between Build Management and Release Management?
When will conduct build verification and end to end testing?
Build Management is managing the issue fixture tasks in the builds whereas Release management is managing the functionality to be incorporated in the Release.
Build Verification Test (BVT) is done when the build is first received by the testers. The basic functionality is checked with valid data. This is done to check whether the build is testable or not. This is done by testers.
End to End testing is also called system testing. Done by senior test engineers or Test lead.
93. What is boundary value analysis (BVA)? What is the use of it?
Boundary value analysis is a technique for test data selection. Test engineer chooses the values that lie along the data extreams.It includes max, minimum, just inside, just out side, typical values and error values.
Boundary Value Analysis is a technique used for writing the test cases. For example: If a particular field accepts the
Values from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001, 999, 2.
I.e. we check on the boundaries and then
Minimum-1, minimum +1 and maximum+1, maximum-1.
94. What is equivalence class partition(ECP)? What is the use of it?
Aquaplane nothing but select the valid and valid class’s example as per client requirement the edit box access only
3-5 capital alphabets then we divided in esp. like valid values only A-Z invalid values are a-z and special characters like ^,8<% 95. If there is no sufficient time for testing & u have to complete the testing, then what will u do?
When I have less time to test the Product then I will take these following steps—
1) Sanity or smoke testing
2) Usability Testing
3) Formal Functionality and GUI Testing
4) Walk through with the Product
96. What is meaning by prototype in SDLC?
This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer’s exact expectation. After a finite number of iterations, the final software package is
Given to the customer. In this methodology, the software is devolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model - as it is very difficult (even for a whiz kid!)
To comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies.
New versions of a software product evolve as a result of prototyping.
97. What is difference between desktop and web application?
The biggest d/f b/w Desktop and web application is- Desktop App (DA) is the machine independent, hence every change has only reflects at the machine level. Where as Web App (WA) is the Internet dependent program, hence any change in the program reflects at every where, where it becomes use. EX……
Suppose there are 5 machines in DA, 5 times installed individually at every machine and if there is any change made in DA then at every machine change has to be made. In WA where the program or Application at the Server or at the one common machine, then if changes made at only central or server or common machine all the changes get reflected at
Every client machine.
98. Difference between application testing and product testing?
Product testing means when any company does testing for their own (company’s) product ex… Norton Antivirus is the Symantec’s product; if Symantec test the Norton i.e. called
As the Product testing. Where as if any company take some projects from some other
Companies like ABC Company takes projects from IBM and test that project on some charges i.e. called as Application Testing.
99. What is a broken link in web testing and how test it?
When we clicked on Hyper link if it opens Page can’t be displayed then that Hyper link is called as broken link.
100: What is CMM level? I need the answer in detail.
The Capability Maturity Model for Software describes the principles and practices underlying software process maturity and is intended to help software organizations improve the maturity of their software processes in terms of an evolutionary path from ad hoc chaotic processes to mature disciplined software processes. The CMM is organized into five maturity levels