“The process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specified requirements or to identify differences between expected and actual results..."
2. What is the Purpose of Testing?
i. To uncover hidden error.
ii. To achieve the maximum usability of the system
iii. To demonstrate expected performance of the system.
3. What types of testing do testers perform?
i. Black-box testing, White box testing is the basic type of testing testers Performs. Apart from that they also perform a lot of tests like
ii. Ad-Hoc testing
iii. Cookie testing
iv. CET (Customer Experience test)
v. Client-Server Test
vi. Configuration Tests
vii. Compatibility testing
viii. Conformance Testing
ix. Depth Test
x. Error Test
xi. Event-Driven
xii. Full Test
xiii. Negative Test
xiv. Parallel Testing
xv. Performance Testing
xvi. Recovery testing
xvii. Sanity Test
xviii. Security Testing
xix. Smoke testing
xx. Web Testing
4. What is the Outcome of Testing?
A stable application, performing its task as expected.
5. What is the need for testing?
The Primary need is to match requirements get satisfied with the functionality and also to answer two questions
A. Whether the system is doing what it supposes to do?
B. Whether the system is not performing what it is not suppose to do?
6. What are the entry criteria for Functionality and Performance testing?
Functional testing:
Functional Spec/ BRS (CRS) / User Manual. An integrated application, Stable for testing
Performance Testing:
Same above mentioned baseline document support and good and healthy application that supports drastic performance testing
7. What is test metrics?
After doing the actual testing, an evaluation doing on the testing to extract some
information about the application health using outputs of testing. Software metrics is any type of measurement, which relates to a software system, process or related documentation.
Eg: Size of code and Found bugs on that count Number of bugs reported per day.
i. Number of Conditions/Cases tested per day
ii. It can be
iii. Test Efficiency
iv. Total number of tests executed
8. Why do you go for White box testing, when Black box testing is available?
A benchmark that certifies Commercial (Business) aspects and also functional (technical) aspects is objectives of black box testing. Here loops, structures, arrays, conditions, files, etc., are very micro level but they are Basement for any application, So White box takes these things in Macro level and test these things
9. What are the entry criteria for Automation testing?
Application should be stable.
Clear Design and Flow of the application is needed
10. When to start and Stop Testing?
If we follow ‘Waterfall’ model then testing can be started after coding. If ‘V’ model is followed then testing can be started at design phase itself. Regard less of model the following criteria should considered
To start:
i. When test Environment was supportive enough for testing.
ii. When Application study was confident enough
To Stop:
i. After full coverage of Scope of testing
ii. After getting enough confidence on health of the application.
11. What is Quality?
“Fitness to use”
“A journey towards excellence”
12. What is Baseline document, Can you say any two?
A baseline document, which starts the understanding of the application before the tester, starts actual testing.
i. Functional Specification
ii. Business Requirement Document
13. What is verification?
A tester uses verification method to ensure the system complies with an organization standards and processes, relying on review or non executable methods (such as software, hardware, documentation and personnel)
“Are we Building the Right Product”
14. What is validation?
Validation physically ensures that the system operates according to plan by Executing thesystem functions through series of tests that can be observed or evaluated.
“Are we building the Product Right”
15. What is quality assurance?
A planned and systematic pattern for all actions necessary to provide adequate
confidence that the item or product conforms to established technical requirements.
16. What is quality control?
Quality Control is defined as a set of activities or techniques whose purpose is to ensure that all quality requirements are being met. In order to achieve this purpose, processes are monitored and performance problems are solved.
17. What are SDLC and TDLC?
The Flow and explanation process, which clearly pictures how a software development and testing should be done, were explained in SDLC and TDLC respectively. (Software development Life Cycle and testing development Life cycle)
TDLC is a informal concept and also referred as TLC
18. What are the Qualities of a Tester?
i. Should be perfectionist
ii. Should be tactful and diplomatic
iii. Should be innovative and creative
iv. Should be relentless
v. Should possess negative thinking with good judgment skills
vi. Should possess the attitude to break the system
19.What are the various levels of testing?
i. Unit Testing
ii. Integration testing
iii. System Testing
iv. User Acceptance Testing
20. Tell names of some testing type which you learnt or experienced?
Any 5 or 6 types which are related to companies profile is good to say in the interview,
i. Ad - Hoc testing
ii. Cookie Testing
iii. CET (Customer Experience Test)
iv. Client-Server Test
v. Configuration Tests
vi. Compatibility testing
vii. Conformance Testing
viii. Depth Test
ix. Error Test
x. Event-Driven
xi. Full Test
xii. Negative Test
xiii. Parallel Testing
xiv. Performance Testing
xv. Recovery testing
xvi. Sanity Test
xvii. Security Testing
xviii. Smoke testing
xix. Web Testing
21. What exactly is Heuristic checklist approach for unit testing?
It is method of achieving the most appropriate solution of several found by alternative methods is selected at successive stages testing. The check list Prepared to Proceed is called Heuristic check list
22. After completing testing, what would you deliver to the client?
i. Test deliverables namely
ii. Test plan
iii. Test Data
iv. Test design Documents (Condition/Cases)
v. Defect Reports
vi. Test Closure Documents
vii. Test Metrics
23. What is a Test Bed?
Before Starting the Actual testing the elements which supports the testing activity such as Test data, Data guide lines. Are collectively called as test Bed.
24. What is a Data Guideline?
Data Guidelines are used to specify the data required to populate the test bed and prepare test scripts. It includes all data parameters that are required to test the conditions derived from the requirement / specification The Document, which supports in preparing test data are called Data guidelines
25. Why do you go for Test Bed?
When Test Condition is executed its result should be compared to Test result (expected result), as Test data is needed for this here comes the role of test Bed where Test data is made ready.
26. What is Severity and Priority and who will decide what?
Severity:
How much the Bug found is supposed to affect the systems Function/Performance, Usually we divide as Emergency, High, Medium, and Low.
Priority:
Which Bug should be solved fist in order of benefit of system’s health? Normally it starts from Emergency giving first Priority to Low as last Priority.
27. Can Automation testing replace manual testing? If it so, how?
Automated testing can never replace manual Testing. As these tools to Follow GIGO principle of computer tools. Absence of creativity and innovative thinking.
But
1. It speeds up the process. Follow a clear Process, which can be reviewed easily.
Better Suited for Regression testing of Manually tested Application and Performance testing.
28. What is a test case?
A Test Case gives values / qualifiers to the attributes that the test condition can have. Test cases, typically, are dependent on data / standards.
A Test Case is the end state of a test condition, i.e., it cannot be decomposed or
broken down further. Test Case design techniques for Black box Testing.
i. Decision table
ii. Equivalence Partitioning Method
iii. Boundary Value Analysis
iv. Cause Effect Graphing
v. State Transition Testing
vi. Syntax Testing
29. What is a test condition?
A Test Condition is derived from a requirement or specification. It includes all possible combinations and validations that can be attributed to that requirement/specification.
30. What is the test script?
A Test Script contains the Navigation Steps, Instructions, Data and Expected Results required to execute the test case(s). Any test script should say how to drive or swim through out the application even for a new user.
31. What is the test data?
The value which are given at expected places(fields) in a system to verify its functionality have been made ready in a piece of document called test data.
32. What is an Inconsistent bug?
The Bug which is not occurring in a definable format or which cannot be caught, even if a process is followed. It may occur and may not when tested with same scenario.
33. What is the difference between Re-testing and Regression testing?
Retest-To check for a particular bug and its dependencies after it is said to be fixed.
Regression testing: To check for the added or new functionality's effect on the existing ystem
34. What are the different types of testing techniques?
i. White box
ii. Black box
iii. Gray Box
35. What are the different types of test case techniques?
i. Test Case design techniques for Black box Testing.
ii. Decision table
iii. Equivalence Partitioning Method
iv. Boundary Value Analysis
v. Cause Effect Graphing
vi. State Transition Testing
vii. Syntax Testing
36. What are the risks involved in testing?
i. Resource Risk (A. Human Resource B. Hardware resource C. Software resource)
ii. Technical risk
iii. Commercial Risk
37. Differentiate Test bed and Test Environment?
Test bed holds only testing documents which supports testing which includes Test data, ata guidelines etc.
Test environment includes all supportive elements namely hardware, software, tools, rowsers, Servers, etc.,
38. What ifs the difference between defect, error, bug, failure, fault?
Error:
“Is an undesirable deviation from requirements?”
Any problem or cause for many problems which stops the system to perform its
functionality is referred as Error
Bug:
Any Missing functionality or any action that is performed by the system which is not upposed to be performed is a Bug.
“Is an error found BEFORE the application goes into production?”
Any of the following may be the reason for birth of Bug
1. Wrong functionality
2. Missing functionality
3. Extra or unwanted functionality
Defect:
A defect is a variance from the desired attribute of a system or application.
“Is an error found AFTER the application goes into production?”
Defect will be commonly categorized into two types:
1. Defect from product Specification
2. Variance from customer/user expectation.
Failure:
Any Expected action that is suppose to happen if not can be referred as failure or we can say Absence of expected response for any request.
Fault:
This generally referred in hardware terminologies. A Problem, which cause the system not to perform its task or objective.
39. What is the difference between quality and testing?
“Quality is giving more cushions for user to use system with all its expected
characteristics” It is usually said as Journey towards Excellence. Testing is an activity done to achieve the quality.
40. What is the difference between White & Black Box Testing?
White box: Structural tests verify the structure of the software itself and require complete access to the object's source code. This is known as ‘white box’ testing because you see into the internal workings of the code.
Black Box: Functional tests examine the observable behavior of software as evidenced by its outputs without reference to internal functions. Hence ‘black box’ testing. If the program consistently provides the desired features with acceptable performance, then specific source code features are irrelevant. It's a pragmatic and down-to-earth assessment of software.
41. What is the difference between Quality Assurance and Quality Control?
QA: Study on Process followed in Project development
QC: Study on Project for its Function and Specification
42. What is the difference between Testing and debugging?
Testing is done to find bugs
Debugging is an art of fixing bugs.
Both are done to achieve the quality
43. What is the difference between bug and defect?
Bug:
Any Missing functionality or any action that is performed by the system which is not supposed to be performed is a Bug.
“Is an error found BEFORE the application goes into production?”
Any of the following may be the reason for birth of Bug
1. Wrong functionality
2. Missing functionality
3. Extra or unwanted functionality
Defect:
A defect is a variance from the desired attribute of a system or application.
“Is an error found AFTER the application goes into production?”
Defect will be commonly categorized into two types:
1. Defect from product Specification
2. Variance from customer/user expectation
44. What is the difference between verification and validation?
Verification:
The process of determining whether of not the products of a given phase of the software development cycle meets the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.
In other words we can say Verification as
“Are we Building the Right Product”
A tester uses verification method to ensure the system complies with an organization standards and processes, relying on review or non executable methods (such as software, hardware, documentation and personnel)
Validation:
The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The technique for validation is testing, inspection and reviewing.
In other words we can say Verification as
“Are we building the Product Right”
Validation physically ensures that the system operates according to plan by Executing the system functions through series of tests that can be observed or evaluated.
45. What is the difference between functional spec? And Business requirement Specification?
Functional specification will be more technical, It holds properties of a field and
functionality dependencies E.g.: size, Type of data whether numeric or alphabets etc.
Business Requirement Specification will be more business oriented which throws light more on needs or requirements
46. What is the difference between unit testing and integration testing?
Unit Testing: Testing of single unit of code, module or program. it is usually done by the developer of the unit. It validates that the software performs as designed. Deliverable of the unit testing is software unit ready for testing with other system components.
Integration Testing: Testing of related programs, modules or units of code. Validates that multiple parts of the system perform as per specification.
Deliverable of integration testing is parts of system ready for testing with other portions of system.
47. What is difference between Volume & Stress?
Volume testing is increasing the volume of data to maximum withstand capacity of the system.
Stress is the combination of both volume and load, so need not to increase in volume alone even user can also increased objective here is to check the up to which extend it can bare the increasing load and volume.
48. What is the difference between Stress & Load Testing?
Stress is the combination of both volume and load, so need not to increase in volume alone even user can also increased objective here is to check the up to which extend it can bare the increasing load and volume.
Load Testing is increasing number of user to maximum withstand capacity of the system.
49. What is the difference between Client Server & Web Based Testing?
Client server needs a Client server environment that is a system to Request and another to respond to its request.
Web Based testing normally goes with 3W sites testing, done to check its stability and functionality when goes online.
50. What is the Difference between Code Walkthrough & Code Review?
Both are almost same except in one issue that is Walkthrough need not be done by people inside the team are who have more knowledge about the system.
Review is highly recommended to be done by people of higher level in team or who have good knowledge about the application.
51. What is the difference between walkthrough and inspection?
Walkthrough:
In a walk through session, the material being examined is presented by a reviewed and evaluated by a team of reviewers.
A walk through is generally carried out without any plan or preparation. the aim of this review is to enhance the process carried out in production environment.
Inspections:
Design and code inspection was first described by FAGUN.
There are three separate inspection performed, they are
Following design, but prior to implementation.
Following implementation, but prior to Unit testing.
Finally inspecting Unit testing, this was not considered to be cost-effective in discovering errors.
52. What is the Difference between SIT & IST?
SIT can be done when system is on the process of integration,
IST need integrated System of various Unit levels of independent functionality and checks its workability after integration and compares it before integration.
53. What is the Difference between static and dynamic?
· Static testing: Testing performed with expecting any response for specific request placed at that time. Done Based on structures, Algorithms, logic, etc.,
· Dynamic testing: Performed to the System that responds to any specific request. More than all that without executing the application this testing cannot be done.
54. What are the Minimum requirements to start testing?
i. Baseline Documents.
ii. Stable application.
iii. Enough hardware and software support E.g. Browsers, Servers, and Tools)
iv. Optimum maintenance of resource
55. What is Smoke Testing & when it will be done?
A quick-and-dirty test that the major functions of a piece of software work without
bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
56. What is Ad hoc testing? When it can be done?
Appropriate and very often syndicated when tester wants to become familiar with the product, or in the environment when technical/testing materials are not 100% completed. It is also largely based on general software product functionality/testing understanding and the normal 'Human Common Sense'.
This can be performed even with non-availability of of Baseline documents.
57. What is cookie testing?
Cookie is a text file normally written by web applications to store all your login-id,
password validation and details about your session. Cookies will get stored in our
machines (client).Its mainly to verify whether cookies are being written correctly. .
Importance of cookie testing:
To evaluate the performance of a web application
To assure the health of www application where more cookies are involved
58. What is security testing?
To test how the system can defense itself from external attacks.
How much it can with stand from breaking the system from performing its assigned task.
Many critical software applications and services have integrated security measures against malicious attacks. The purpose of security testing of these systems include identifying and removing software flaws that may potentially lead to security violations, and validating the effectiveness of security measures. Simulated security attacks can be performed to find vulnerabilities.
59. What is database testing?
The demonstrate the backend response for front end requests
How backend, which stores and retrieve back the data and supports the front end when inneed is justified database testing.
60. What is the relation ship between Quality & Testing?
Quality is a journey towards excellence; Testing is the way of achieving quality.
61. How do you determine, what to be tested?
The Scope of testing should be created based on the requirements or needs given by the end user or client, based on these things the testing scope should be decided.
62. How do you go about testing a project?
i. System study
ii. Understanding the application
iii. Test environment setup
63. What is the Initial Stage of testing?
Right from understanding the application testing starts with clarifying the ambiguities in the application and continues to Test initiation encloses, Test process, test data, Data guidelines Preparation and test design which is finally executed
64. What is Web Based Application Testing?
Web Based testing normally goes with 3W sites testing, done to check its stability and functionality when goes online.
65. What is Client Server Application Testing?
Client server needs a Client server environment that is a system to Request and another to respond to its request.
66. What is the use of Functional Specification?
Functional Specification is a baseline document prepared in technical perspective, says how the system should behave in ideal scenario. Tells right from syntax to its functionality and dependencies
Eg: for a password and user id fields
It should accept
67. Why do we prepare test condition, test cases, test script (Before Starting Testing)?
These are test design document which are used to execute the actual testing
Without which execution of testing is impossible ,finally this execution is going to find the bugs to be fixed so we have prepare this documents.
68. Is it not waste of time in preparing the test condition, test case & Test Script?
No document prepared in any process is waste of time, That too test design documents which plays vital role in test execution can never be said waste of time as without which proper testing cannot be done.
69. How do you go about testing of Web Application?
To approach a web application testing, the first attack on the application should be on its performance behavior as that is very important for a web application and then transfer of data between web server ,front end server, security server and back end server.
70. How do you go about testing of Client Server Application?
To approach a client server environment we can track back the data transfer, Check the compatibility and verify the individual behavior and then to compare as client and server.
71. What is meant by Static Testing?
Structure of a program, Program Logic, Condition coverage, Code coverage etc. can be tested. Analysis of a program carried out without executing the program.
72. Can the static testing be done for both Web & Client Server Application?
Yes, Can be done regardless of type of application, but Depends on the Application’s individual structure and behavior.
73. In the Static Testing, what all can be tested?
i. Functions,
ii. Conditions
iii. Loops
iv. Arrays
v. Structures
74. Can test condition, test case & test script help you in performing the static testing?
Static testing will be done based on Functions, Conditions, loops, arrays and structures. so hardly not needed to have These documents, By keeping this also static testing can be done.
75. What does dynamic testing mean?
Any dynamic application i.e., the system that responds to request of user is tested by executing it is called dynamic testing
76. Is the dynamic testing a functional testing?
Yes, Regardless of static or dynamic if applications functionality's are attacked keeping in mind to achieve the need then it will come under functional testing.
77. Is the Static testing a functional testing?
Yes, Regardless of static or dynamic if applications functionality's is attacked keeping in mind to achieve the need then it will come under functional testing.
78. What is the functional testing you perform?
I have done Conformance testing, Regression testing, Workability testing, Function Validation and Field level validation testing.
79. What is meant by Alpha Testing?
Alpha testing is testing of product or system at developer’s site by the customer.
80. What kind of Document you need for going for a Functional testing?
Functional specification is the ultimate document, which expresses all the functionality's of the application and other documents like user manual and BRS are also need for functional testing.
Gap analysis document will add value to understand expected and existing system.
81. What is meant by Beta Testing?
User Acceptance testing which is done with the objective of achieving all users needs. In this testing usually users or testers will involve in performing.
E.g.: a Product after completion given to customers for trail as Beta version and feedback from users and important suggestions which will add quality will be done before release.
82. At what stage the unit testing has to be done?
After completing coding of individual functionality's unit testing can be done.
Say for E.g.: if an application have 5 functionality's to work together, if they have been developed individually then unit testing can be carried out before their integration is suppose to be done.
Who can perform the Unit Testing?
Both developers and testers can perform this unit level testing
83.What is the testing that a tester performs at the end of Unit Testing?
Integration testing will be performed after unit testing to ensure that unit tested modules get integrated correctly.
84. What are the things, you prefer & Prepare before starting Testing?
Study the application, Understanding the applications expected functionality's, Preparing Test plan, Ambiguity/Clarification Document and test design
Documents.
85. What is Integration Testing?
Integration testing exercises several units that have been combined to form a module, subsystem, or system. Integration testing focuses on the interfaces between units, to make sure the units work together. The nature of this phase is certainly 'white box', as we must have certain knowledge of the units to recognize if we have been successful in fusing them together in the module.
86. What is Incremental Integration Testing?
Incremental Integration Testing is an approach of testing where we will integrate the modules top to bottom or on the incrementing scale of intensity.
87. What is meant by System Testing?
The system test phase begins once modules are integrated enough to perform tests in a whole system environment. System testing can occur in parallel with integration test, especially with the top-down method.
88. What is meant by SIT?
System Integration Testing done after the completion of Unit level testing. An application which is integrated together after assuring their individual functionality's.
89. When do you go for Integration Testing?
When all Separate unit in Unit Level testing is assured to do good their performance, Then Application is recommended for integration after these unit getting integrated, application can be performed integration testing.
90. Can the System testing be done at any stage?
No, The system as a whole can be tested only if all modules are integrated and all modules work correctly
System testing should be done before UAT (User Acceptance testing) and Before Unit Testing.
91. What are stubs & drivers?
Driver programs provide emerging low-level modules with simulated inputs and the necessary resources to function. Drivers are important for bottom-up testing, where you have a complete low-level module, but nothing to test it with.
Stubs simulate sub-programs or modules while testing higher-level routines.
92. What is the Concept of Up-Down & Down-Up in Testing in integration testing?
There is two approach in testing an application if the functionality sequence was mapped and tracked from top to bottom then it is called top down method ,If that was done for integration testing then it is top down model testing in Integration and vice versa for Bottom up model
93. What is the final Stage of Integration Testing?
All the individual units integrated together to Perform a task as a system or Part of the system as expected to do so.
94. Where in the SDLC, the Testing Starts?
It depends upon the Software Model which we follow. If we use Waterfall model then testing will comes in to picture only after coding is done. If we follow V model then testing can be started at the design phase itself. UAT test cases can be written from URS/BRS and System test cases can be written from SRS.
95. What is the Outcome of Integration Testing?
At the completion of integration testing all the unit level functionalities or sub modules are integrated together and finally it should work as a system as whole as expected.
96. What is meant by GUI Testing?
Testing the front-end user interfaces to applications, which use GUI support systems and standard such as MS Windows.
97. What is meant by Back-End Testing?
Database Testing is also called as back end testing checking whether database elements have been accessed by front end whenever required as desired.
98. What are the features, you take care in Prototype testing?
Prototype testing is carrying out testing in same method reputedly to understand the system behavior; here full coverage of functionality should be taken care With the same process followed as for Prototype testing.
99. What is Mutation testing & when can it be done?
Mutation testing is a powerful fault-based testing technique for unit level testing. Since it is a fault-based testing technique, it is aimed at testing and uncovering some specific kindsof faults, namely simple syntactic changes to a program. Mutation testing is based on two assumptions: the competent programmer hypothesis and the coupling effect. The competent programmer hypothesis assumes that competent programmers tend to write nearly "correct" programs. The coupling effect stated that a set of test data that can uncover all simple faults in a program is also capable of detecting more complex faults. Mutation testing injects faults into code to determine optimal test inputs
100. What is Compatibility Testing?
Testing to ensure compatibility of an application with different browsers, Operating Systems, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.
101. What is Usability Testing?
Usability testing is a core skill because it is the principal means of finding out whether a system (see our definition below) meets its intended purpose. All other skills that we deploy or cultivate aim to make usability (and, ultimately, use) successful.
It is a Process of Testing the effectiveness, efficiency, and satisfaction with which
specified users could achieve specified goals in the Application. Synonymous with "ease of use".
102. What is the Importance of testing?
Software Testing is more Oriented to detecting the defects or often equated to finding bugs. Testing is mainly done to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. Testing only demonstrates that the product performs each function intended & to show the product is free from defect.
103. What is meant by regression Testing?
Regression testing is an expensive but necessary activity performed on modified softwareto provide confidence that changes are correct and do not adversely affects other system components. Four things can happen when a developer attempts to fix a bug. Three of these things are bad, and one is good:
Because of the high probability that one of the bad outcomes will result from a change to the system, it is necessary to do regression testing.
104. When we prefer Regression & what are the stages where we go for Regression Testing?
We Prefer regression testing to provide confidence that changes are correct & has not affected the flow or Functionality of an application which got Modified or bugs got fixed in it.
Stages where we go for Regression Testing are: -
Minimization approaches seek to satisfy structural coverage criteria by identifying a minimal set of tests that must be retested, for identifying whether the application works fine.
Coverage approaches are also based on coverage criteria, but do not require minimization of the test set. Instead, they seek to select all tests that exercise changed or affected program components.
Safe attempt instead to select every test that will cause the modified program to produce different output than original program.
105. What is performance testing?
An important phase of the system test, often-called load, volume or performance test, and stress tests try to determine the failure point of a system under extreme pressure. Stress tests are most useful when systems are being scaled up to larger environments or being implemented for the first time. Web sites, like any other large-scale system that requires multiple accesses and processing, contain vulnerable nodes that should be tested before deployment. Unfortunately, most stress testing can only simulate loads on various points of the system and cannot truly stress the entire network, as the users would experience it. Fortunately, once stress and load factors have been successfully overcome, it is only necessary to stress test again if major changes take place.
A drawback of performance testing is that can easily confirm that the system can handle heavy loads, but cannot so easily determine if the system is producing the correct information. In other words, processing incorrect transactions at high speed can cause much more damage and liability than simply stopping or slowing the processing of correct transactions.
Performance testing can be applied to understand your application or WWW site's scalability, or to benchmark the performance in an environment of third party products such as servers and middleware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
The following three types highly influence Performance of an application.
Load testing, Volume testing, Stress Testing
Stress testing is the combination of both load and volume.
106. What is the Performance testing; those can be done Manually & Automatically?
This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
Manually: - Load, Stress, & Volume are the types of testing which are been done
Manually.
Automated: - Load, Stress, & Volume are the types of testing which are been done automatically, by using the Automated Skills.
107. What is Volume, Stress & Load Testing?
Volume testing: - Testing the Application under varying loads; keeping the Number of Users constantly & finding the Response time & the system With Standing Capability or varying the Load till saturation Point is reached
Load Testing : -Testing the Application under Constant load; keeping varying the Number of Users & there by finding the Response time & the system With Standing Capability or varying the Users till saturation Point is reached
Stress Testing : - Testing the Application under varying loads; keeping varying the Number of Users simultaneously & there by finding the Response time & the system With Standing Capability or varying the Load & Users till saturation Point is reached
108. What is a Bug?
Bug: - “Is an error found BEFORE the application goes into production?”
109. What is a Defect?
Defect: - “Is an error found AFTER the application goes into production?”
110. What is the defect Life Cycle?
Test Team (Here the Defect status will be Open)
Test Lead Authorize the bugs found (Here the Defect Status will be Open)
Development Team reviewing the Defect (Here the Defect Status will be Open)
The defect can be Authorized or Unauthorized by the development Team (Here the Status of the Defect will be Open (For Authorized Defects) & Reject (For Unauthorized Defects)
Development Team fixing the Defect (Here the authorized Bugs will get fixed or differed; it is done again by the Development team. Here the Status after the Development team fixing the bugs will be (Fixed) & Status will be Differed for the bugs which got Differed)
The Fixed bugs will be again Re-tested by the Test Team (Here based on the Closure of the Bug, the status will be made as closed or if the Defect still remains, it will be Re-raised again & even the new bugs with status Open will be sent to the Development team)
The above-mentioned cycle flows on continuously, until all the bugs gets fixed in the application.
111. What is the Priority in fixing the Bugs?
Priority: - The value will be given to the bugs, by both Testers & Developers (But Mostly the Development team will take care of this). It mainly deals with, what importance should be given to each bug by the Developer. (i.e.) like the Critical bugs should be solved first & then the Major bugs can be taken care.
112. Explain the Severity you rate for the bugs found?
i. Emergency
ii. High (Very High & high)
iii. Medium
iv. Low (Very Low & Low)
Testers will rate severity; it is based on the Defect we find in the application. Severity can be rated as Critical or major or Minor. It is mostly done based on the nature of the defect found in the Application.
Eg: - When user is not able to proceed or system gets crashes & so that tester is not able to proceed further testing (These Bugs will be rated as Critical)
E.g.: - When user tries to add an record & then tries to view the same record added & if the details getting displayed to the fields are not the same which the user provided as the value to the fields (These Type of Bugs will be rated as Major Bugs)
E.g.: - Mostly the FLV Bugs & some functional bugs (Related the value display etc.) will be rated as Minor.
113. Difference between UAT & IST?
UAT & IST
UAT: -
1. Done Using BRD
2. Done with the Live Data
3. Testing is done in User Style
4. Testing in done in the Client Place
5. Testing is done by the Real Users or some Third Party Testers
IST: -
1. Done Using FS
2. Done with the Simulated Data
3. Testing is done in a Controlled Way.
4. Testing in done in Offsite
5. Testing is done in the Testers Company
114. What is meant by UAT?
Traditionally, this is where the users ‘get their first crack’ at the software. Unfortunately, by this time, it's usually too late. If the users have not seen prototypes, been involved with the design, and understood the evolution of the system, they are inevitably going to be unhappy with the result. If you can perform every test as user acceptance tests, you have
a much better chance of a successful project
User Acceptance testing is done to achieve the following:-
User specified requirements have been satisfied
Functionality is doing as per supporting documents
Expected performance have been achieved
End user is comfortable to use the application.
115. What all are the requirements needed for UAT?
Business Requirement Document is the Documents required for performing the UAT Testing by the testers.
Application should be Stable (Means, all the Modules should be tested at least once after Integrating the Modules)
116. What are the docs required for Performance Testing?
Bench Mark is the Basic Document required for Performance Testing. Where the
documents contains in detail about the Response Time, Transaction Time, Data Transfer Time, Virtual Memory in which the Application should work.
117. What is risk analysis?
Risk Analysis is a series step that helps the Software or Testing Team to understand & manage Uncertainty. It is a process of evaluating risks, threats, controls, & vulnerabilities.
Threat: - Which is capable of exploiting vulnerability in the security of a
computer system or application.
Vulnerability: -Is a design, implementation, or operations flaw that may be
exploited by a threat?
Control: -Control is anything that tends to cause the reduction of risk.
118. How to do risk management?
Identifying the Risk Involved in the project & finding Mitigation for the Risk Found will do risk Management. Risk Mitigation will be a solution for the Risk Identified.
119. What are test closure documents?
i. Test Conditions
ii. Test Case
iii. Test Plan
iv. Test Strategy
v. Traceability Matrix
vi. Defect Reports
vii. Test Closure Document
viii. Test Data
(The Above Mentioned Deliverables are based on the deliverables accepted by the Testing Team & mentioned in the Test Strategy)
120. What is Traceability matrix?
Traceability Matrix: -
Through out the testing life cycle of the project Traceability matrix has been maintained to ensure the Verification & Validation of the testing is complete.
121. What ways can be followed for defect management?
Reporting the Bugs through the Defect Report (Excel Template)
Any in-house tool inbuilt in the company may also be used.
Commonly available tools like TEST DIRECTOR can also be employed
No comments:
Post a Comment