Manual and Software Testing – FAQ  Part 1

22. April 2019 Uncategorized 0

 

 

  1. What is Monkey Testing?

Perform abnormal action on the application deliberately in order to verify the stability of the application.

  1. What is Usability Testing?

To verify whether the application is user-friendly or not and was comfortably used by an end user or not. The main focus in this testing is to check whether the end user can understand and operate the application easily or not. An application should be self-exploratory and must not require training to operate it.

  1. What is Security Testing?

Security testing is a process to determine whether the system protects data and maintains functionality as intended.

  1. What is Soak Testing?

Running a system at high load for a prolonged period of time to identify the performance problems is called Soak Testing.

  1. What is Endurance Testing?

Endurance testing is a non-functional testing type. It is also known as Soak Testing. Refer Soak testing.

  1. What is Performance Testing?

This type of testing determines or validates the speed, scalability, and/or stability characteristics of the system or application under test. Performance is concerned with achieving response times, throughput, and resource-utilization levels that meet the performance objectives for the project or product.

  1. What is Load Testing?

It is to verify that the system/application can handle the expected number of transactions and to verify the system/application behavior under both normal and peak load conditions.

  1. What is Volume Testing?

It is to verify that the system/application can handle a large amount of data

  1. What is Stress Testing?

It is to verify the behavior of the system once the load increases more than its design expectations.

  1. What is Scalability Testing?

Scalability testing is a type of non-functional testing. It is to determine how the application under test scales with increasing workload.

  1. What is Concurrency Testing?

Concurrency testing means accessing the application at the same time by multiple users to ensure the stability of the system. This is mainly used to identify deadlock issues.

  1. What is Fuzz Testing?

Fuzz testing is used to identify coding errors and security loopholes in an application. By inputting massive amount of random data to the system in an attempt to make it crash to identify if anything breaks in the application.

  1. What is Adhoc Testing?

Ad-hoc testing is quite opposite to the formal testing. It is an informal testing type. In Adhoc testing, testers randomly test the application without following any documents and test design techniques. This testing is primarily performed if the knowledge of testers in the application under test is very high. Testers randomly test the application without any test cases or any business requirement document.

  1. What is Interface Testing?

Interface testing is performed to evaluate whether two intended modules pass data and communicate correctly to one another.

  1. What is Reliability Testing?

Perform testing on the application continuously for long period of time in order to verify the stability of the application

  1. What is Bucket Testing?

Bucket testing is a method to compare two versions of an application against each other to determine which one performs better.

  1. What are the principles of Software Testing?
  1. Testing shows presence of defects
  2. Exhaustive testing is impossible
  3. Early testing
  4. Defect clustering
  5. Pesticide Paradox
  6. Testing is context depending
  7. Absence of error fallacy
  1. What is Exhaustive Testing?

Testing all the functionalities using all valid and invalid inputs and preconditions is known as Exhaustive testing.

  1. What is Early Testing?

Defects detected in early phases of SDLC are less expensive to fix. So conducting early testing reduces the cost of fixing defects.

  1. What is Defect clustering?

Defect clustering in software testing means that a small module or functionality contains most of the bugs or it has the most operational failures.

  1. What is Pesticide Paradox?

Pesticide Paradox in software testing is the process of repeating the same test cases, again and again, eventually, the same test cases will no longer find new bugs. So to overcome this Pesticide Paradox, it is necessary to review the test cases regularly and add or update them to find more defects.

If you are someone who is interested in software testing, join QcMore, the most advanced software testing training institute in Kochi. There are many software testing training courses in Kochi, but what sets us apart is our curriculum that is a perfect blend of theory and practice with lectures and live projects. We also provide a combination of manual training and automation software testing training, so as to equip you with all necessary skills demanded by the industry.