2024年4月26日发(作者：)
Difference between System testing and integration test
Integration Testing: Testing of combined parts of an application to determine if they function
together correctly. Usually performed after unit and functional testing. This type of testing is
especially relevant to client/server and distributed systems.
System Testing: Testing that attempts to discover defects that are properties of the entire
system rather than of its individual components.
Difference between black box testing and white box test
Black Box testing: we test the functionaliy of the application throughly with the help of
requirements. here we do not concern about the internal logic of the code. here we check the
system by giving the proper input whether it gives proper output or not. this work done by
the testers.
White Box testing: we more concern about internal logic of the program i.e; here we check
module interface local datastructures logical conditions on their true and false side loops etc;
designated and executed by the developers/SDET.
Difference between performance, load, and stress testing
Performance testing: Performance testing is used to show that after testing there is no defect
in the system or application. Load testing and stress testing are the parts of performance
testing.
Load Testing: Load testing is used to test the application under a range of loads in order to
determine at what point the system's response time degrades or fails.
For example,If an application is supports 500 users then test whether it supports the no of
users as specified.
Stress Testing: This testing is used to push the system beyond the limits of its specified
requirements to find the potentially harmful bugs. we can say that-"How much is too much
for the system".
Difference between function testing and regression testing
1 / 17
Functional Testing: This test is performed to see weather the program is working as per the
given flow. functionality is working correctly or not as per requiremnet.
Regression Testing: This test is performed during modification stage. where the applied
changes impact the change in working of the whole project or not. Means weather the
modification caused errors in existing working of the project or not
Difference between actual result and expect result
Actual result is the behavior produced/observed when a component or system is tested. It’s
like “what it actually look like” status.
Expect result is the behavior predicted by the specification of the component or system under
specified conditions. It’s like “what it suppose to be” status
Did white box testing means testing of code
Yes ,it test the logic of the code
What are the critical things you listed in the performance test result
1. Concurrent users
2. Throughout
3. Server status such as CPU usage,Memory
4. Response times
5. Time lapses
6. Test environment
What are contents of defects/bugs
A software bug is the common term used to describe an error flaw, mistake, failure, or fault
in a computer program or system that produces an incorrect or unexpected result, or causes
it to behave in unintended ways.
Content of bugs
1. Bug ID
2. Bug Title
3. Summary: expected result, actual result
4. Priority
2 / 17
5. Severity
6. Status:Open/fix/close/holdon/non-reproduce
7. Software Version
8. Platform and OS
9. Component
10. Assign To
11. Environment
12. Reproduce Steps
13. Supporting files, such as snapshot
What are contents of test cases
1. Test Case ID:
2. Case Name
3. Priority
4. Test step
5. Test Execution
6. Expected Results
7. Actual Results
8. Revision history
9. Environment
10. Run time
11. Name of tester, date
What is test plan? Have you ever written test plan?
A test plan is a document detailing a systematic approach to testing a system such as a
machine or software.
Contents of test plan:
1. Test scope
2. Test strategy: integrate testing, system testing, performance testing, security testing
3. Test Risk
4. Test resource
5. Test time line
3 / 17
6. Sign off critical
What is the scope of testing
The scope of testing is the boundaries of testing, what will be tested and what will not be
tested
.What does your test report look like
1. the scope of testing
2. test enviroment
3. Detailed Test result:the case execution and their status
4. bug quantity and severity
5. Suggestion
What is bug triage and triage group? How to resolve conflict when verifying it is a bug or
not
Triage is a process of identify or verify the bugs based on the information of the bug.
Whenever we have disagreement to indentify the bug or for a very complex bug, we assign
the bug to the triage group, a group of Sr. developers, testers, and leads, to verify it.
How to know your test cases are too many or too less
Verify the test cases against the scope of the testing and function requirement
How to ensure the test coverage
1. Ensure that the documents defining the business and customer requirements are
complete and correct.
2. Ensure that testers themselves have thoroughly read and understood the documents.
3. Prepare a clear cut scope of testing based on product documents.
4. The strategy and Test Planning is as per system requirements.
5. Decide test methodology and test tools (if any), and test schedule.
6. Prepare Test Cases based on business rules and customer requirements.
7. Ensure that the test cases are extensive and sensible to cover the complete
requirements testing.
8. Ensure that during testing no changes in the test environment (coding etc.) is done
by development team.
4 / 17
9. Ensure that development team representatives (1 or all) are present during the
complete testing.
10. Create Test Scenarios based on test cases.
11. Observe the result of each test case and record it accordingly.
12. Prepare a comprehensive and detailed test report explaining each of the test case,
scenario and its result elaborately.
13. Ensure that all bugs reported should make sense, no duplication/overlapping
14. The final report submitted should clearly state the areas, reason, impact not covered
under testing if avaliable.
15. Ensure that you have a tentative plan from the dev team when they're fixing all bugs
and submitting it back to testing team.
16. Verify all bugs fixed and ensure that the development team is sitting with testers
during verification.
How to make sure/verify that your testers are blocked by error
1. Verify the build by running build verification test cases
2. Verify the test case steps, script, and data. If the data is spoofed, we also need to
verify the script for spoofing the data
3. Rerun the test cases by other tester (other environment if there is as alternative) for
double check
When should testing be stopped?
1. all the testcases are executed
2. Defect rate follows down below the criteria,Bug rate falls down below the criteria
3. dead line comes
LR面试题
What is load testing?
Load testing is to test that if the application works fine with the loads that result from large
number of simultaneous users, transactions and to determine weather it can handle peak
usage periods.
5 / 17
What is Performance testing?
Timing for both read and update transactions should be gathered to determine whether
system functions are being performed in an acceptable timeframe. This should be done
standalone and then in a multi user environment to determine the effect of multiple
transactions on the timing of a single transaction.
Explain the Load testing process?
Step 1: Planning the test. Here, we develop a clearly defined test plan to ensure the test
scenarios we develop will accomplish load-testing objectives.
Step 2: Creating Vusers. Here, we create Vuser scrīpts that contain tasks performed by each
Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions.
Step 3: Creating the scenario. A scenario describes the events that occur during a testing
session. It includes a list of machines, scrīpts, and Vusers that run during the scenario. We
create scenarios using LoadRunner Controller. We can create manual scenarios as well as
goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load
generator machines, and percentage of Vusers to be assigned to each scrīpt. For web tests,
we may create a goal-oriented scenario where we define the goal that our test has to achieve.
LoadRunner automatically builds a scenario for us.
Step 4: Running the emulate load on the server by instructing multiple Vusers
to perform. tasks simultaneously. Before the testing, we set the scenario configuration and
scheduling. We can run the entire scenario, Vuser groups, or individual Vusers.
Step 5: Monitoring the monitor scenario execution using the LoadRunner
online runtime, transaction, system resource, Web resource, Web server resource, Web
application server resource, database server resource, network delay, streaming media
resource, firewall server resource, ERP server resource, and Java performance monitors.
Step 6: Analyzing test results. During scenario execution, LoadRunner records the
performance of the application under different loads. We use LoadRunner’s graphs and
reports to analyze the application’s performance.
When do you do load and performance Testing?
6 / 17
perform. load testing once we are done with interface (GUI) testing. Modern system
architectures are large and complex. Whereas single user testing primarily on functionality
and user interface of a system component, application testing focuses on performance and
reliability of an entire system. For example, a typical application-testing scenario might
depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what
is the response time of the system, does it crash, will it go with different software
applications and platforms, can it hold so many hundreds and thousands of users, etc. This
is when we set do load and performance testing.
What are the components of LoadRunner?
The components of LoadRunner are The Virtual User Generator, Controller, and the Agent
process, LoadRunner Analysis and Monitoring, LoadRunner Books Online.
What Component of Load Runner would you use to record a script? - The Virtual User
Generator (VuGen) component is used to record a scrīpt. It enables you to develop Vuser
scripts for a variety of application types and communication protocols.
What Component of LoadRunner would you use to play Back the scrīpt in multi user mode?
The Controller component is used to playback the scrīpt in multi-user mode. This is done
during a scenario run where a vuser scrīpt is executed by a number of vusers in a group.
What is a rendezvous point?
You insert rendezvous points into Vuser scrīpts to emulate heavy user load on the server.
Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to
arrive at a certain point, in order that they may simultaneously perform. a task. For
example, to emulate peak load on the bank server, you can insert a rendezvous point
instructing 100 Vusers to deposit cash into their accounts at the same time.
What is a scenario?
A scenario defines the events that occur during each testing session. For example, a scenario
defines and controls the number of users to emulate, the actions to be performed, and the
machines on which the virtual users run their emulations.
7 / 17
Explain the recording mode for web Vuser scrīpt?
We use VuGen to develop a Vuser scrīpt by recording a user performing typical business
processes on a client application. VuGen creates the scrīpt by recording the activity between
the client and the server. For example, in web based applications, VuGen monitors the client
end of the database and traces all the requests sent to, and received from, the database
server. We use VuGen to: Monitor the communication between the application and the
server; Generate the required function calls; and Insert the generated function calls into a
Vuser scrīpt.
Why do you create parameters?
Parameters are like scrīpt variables. They are used to vary input to the server and to
emulate real users. Different sets of data are sent to the server each time the scrīpt is run.
Better simulate the usage model for more accurate testing from the Controller; one scrīpt
can emulate many different users on the system.
What is correlation? Explain the difference between automatic correlation and manual
correlation?
Correlation is used to obtain data which are unique for each run of the scrīpt and which are
generated by nested queries. Correlation provides the value to avoid errors arising out of
duplicate values and also optimizing the code (to avoid nested queries). Automatic
correlation is where we set some rules for correlation. It can be application server specific.
Here values are replaced by data which are created by these rules. In manual correlation,
the value we want to correlate is scanned and create correlation is used to correlate.
How do you find out where correlation is required? Give few examples from your projects? -
Two ways: First we can scan for correlations, and see the list of values which can be
correlated. From this we can pick a value to be correlated. Secondly, we can record two
scrīpts and compare them. We can look up the difference see for the values which needed to
be correlated. In my project, there was a unique id developed for each customer, it was
8 / 17
nothing but Insurance Number, it was generated automatically and it was sequential and
this value was unique. I had to correlate this value, in order to avoid errors while running
my scrīpt. I did using scan for correlation.
Where do you set automatic correlation options?
Automatic correlation from web point of view can be set in recording options and
correlation tab. Here we can enable correlation for the entire scrīpt and choose either issue
online messages or offline actions, where we can define rules for that correlation. Automatic
correlation for database can be done using show output window and scan for correlation
and picking the correlate query tab and choose which query value we want to correlate. If
we know the specific value to be correlated, we just do create correlation for the value and
specify how the value to be created.
What is a function to capture dynamic values in the web Vuser scrīpt? -
Web_reg_save_param function saves dynamic data information to a parameter.
When do you disable log in Virtual User Generator, When do you choose standard and
extended logs?
Once we debug our scrīpt and verify that it is functional, we can enable logging for errors
only. When we add a scrīpt to a scenario, logging is automatically disabled. Standard Log
Option: When you select
Standard log, it creates a standard log of functions and messages sent during scrīpt
execution to use for debugging. Disable this option for large load testing scenarios. When
you copy a scrīpt to a scenario, logging is automatically disabled Extended Log Option:
Select
extended log to create an extended log, including warnings and other messages. Disable this
option for large load testing scenarios. When you copy a scrīpt to a scenario, logging is
automatically disabled. We can specify which additional information should be added to the
extended log using the Extended log options.
9 / 17
发布评论