Types of Software Testing: Different Testing Types with Details

By Sruthy

By Sruthy

Sruthy, with her 10+ years of experience, is a dynamic professional who seamlessly blends her creative soul with technical prowess. With a Technical Degree in Graphics Design and Communications and a Bachelor’s Degree in Electronics and Communication, she brings a unique combination of artistic flair…

Learn about our editorial policies.
Updated December 19, 2024
Edited by Kamila

Edited by Kamila

Kamila is an AI-based technical expert, author, and trainer with a Master’s degree in CRM. She has over 15 years of work experience in several top-notch IT companies. She has published more than 500 articles on various Software Testing Related Topics, Programming Languages, AI Concepts,…

Learn about our editorial policies.

Get a comprehensive understanding of the various Types of Software Testing. Pick the right testing approach for your project to navigate the diverse landscape of software testing methodologies:

We, as testers, are aware of the various types of Software Testing like Functional Testing, Non-Functional Testing, Automation Testing, Agile Testing, and their sub-types, etc.

Each of us would have come across several types of testing on our testing journey. We might have heard some and we might have worked on some, but not everyone has knowledge about all the testing types.

Each type of testing has its own features, advantages, and disadvantages as well. However, in this tutorial, we have covered mostly each and every type of software testing which we usually use in our day-to-day testing life.

Let’s have a look at them!!

Different Types of Software Testing

Different Types of Software Testing

Here is the high-level classification of Software testing types.

We will see each type of testing in detail with examples.

Classification of Software testing types

Functional Testing

There are four main types of functional testing.

#1) Unit Testing

Unit testing is a type of software testing which is done on an individual unit or component to test its corrections. Typically, Unit testing is done by the developer at the application development phase. Each unit in unit testing can be viewed as a method, function, procedure, or object. Developers often use test automation tools such as NUnit, Xunit, JUnit for the test execution.

Unit testing is important because we can find more defects at the unit test level.

For example, there is a simple calculator application. The developer can write the unit test to check if the user can enter two numbers and get the correct sum for addition functionality.

a) White Box Testing

White box testing is a test technique in which the internal structure or code of an application is visible and accessible to the tester. In this technique, it is easy to find loopholes in the design of an application or fault in business logic. Statement coverage and decision coverage/branch coverage are examples of white box test techniques.

b) Gorilla Testing

Gorilla testing is a test technique in which the tester and/or developer test the module of the application thoroughly in all aspects. Gorilla testing is done to check how robust your application is.

For example, the tester is testing the pet insurance company’s website, which provides the service of buying an insurance policy, tag for the pet, Lifetime membership. The tester can focus on any one module, let’s say, the insurance policy module, and test it thoroughly with positive and negative test scenarios.

#2) Integration Testing

Integration testing is a type of software testing where two or more modules of an application are logically grouped together and tested as a whole. The focus of this type of testing is to find the defect on interface, communication, and data flow among modules. Top-down or Bottom-up approach is used while integrating modules into the whole system.

This type of testing is done on integrating modules of a system or between systems. For example, a user is buying a flight ticket from any airline website. Users can see flight details and payment information while buying a ticket, but flight details and payment processing are two different systems. Integration testing should be done while integrating of airline website and payment processing system.

a) Gray box testing

As the name suggests, gray box testing is a combination of white-box testing and black-box testing. Testers have partial knowledge of the internal structure or code of an application.

#3) System Testing

System testing is types of testing where tester evaluates the whole system against the specified requirements.

a) End to End Testing

It involves testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

For example, a tester is testing a pet insurance website. End to End testing involves testing of buying an insurance policy, LPM, tag, adding another pet, updating credit card information on users’ accounts, updating user address information, receiving order confirmation emails and policy documents.

b) Black Box Testing

Blackbox testing is a software testing technique in which testing is performed without knowing the internal structure, design, or code of a system under test. Testers should focus only on the input and output of test objects.

Detailed information about the advantages, disadvantages, and types of Black Box testing can be found here.

c) Smoke Testing

Smoke testing is performed to verify that basic and critical functionality of the system under test is working fine at a very high level.

Whenever a new build is provided by the development team, then the Software Testing team validates the build and ensures that no major issue exists. The testing team will ensure that the build is stable, and a detailed level of testing will be carried out further.

For example, tester is testing pet insurance website. Buying an insurance policy, adding another pet, providing quotes are all basic and critical functionality of the application. Smoke testing for this website verifies that all these functionalities are working fine before doing any in-depth testing.

d) Sanity Testing

Sanity testing is performed on a system to verify that newly added functionality or bug fixes are working fine. Sanity testing is done on stable build. It is a subset of the regression test.

For example, a tester is testing a pet insurance website. There is a change in the discount for buying a policy for second pet. Then sanity testing is only performed on buying insurance policy module.

e) Happy path Testing

The objective of Happy Path Testing is to test an application successfully on a positive flow. It does not look for negative or error conditions. The focus is only on valid and positive inputs through which the application generates the expected output.

f) Monkey Testing

Monkey Testing is carried out by a tester, assuming that if the monkey uses the application, then how random input and values will be entered by the Monkey without any knowledge or understanding of the application.

The objective of Monkey Testing is to check if an application or system gets crashed by providing random input values/data. Monkey Testing is performed randomly, no test cases are scripted, and it is not necessary to be aware
of the full functionality of the system.

#4) Acceptance Testing

Acceptance testing is a type of testing where client/business/customer test the software with real time business scenarios.

The client accepts the software only when all the features and functionalities work as expected. This is the last phase of testing, after which the software goes into production. This is also called User Acceptance Testing (UAT).

a) Alpha Testing

Alpha testing is a type of acceptance testing performed by the team in an organization to find as many defects as possible before releasing software to customers.

For example, the pet insurance website is under UAT. UAT team will run real-time scenarios like buying an insurance policy, buying annual membership, changing the address, ownership transfer of the pet in a same way the user uses the real website. The team can use test credit card information to process payment-related scenarios.

b) Beta Testing

Beta Testing is a type of software testing which is carried out by the clients/customers. It is performed in the Real Environment before releasing the product to the market for the actual end-users.

Beta Testing is carried out to ensure that there are no major failures in the software or product, and it satisfies the business requirements from an end-user perspective. Beta Testing is successful when the customer accepts the software.

Usually, this testing is typically done by the end-users. This is the final testing done before releasing the application for commercial purposes. Usually, the Beta version of the software or product released is limited to a certain number of users in a specific area.

So, the end-user uses the software and shares the feedback with the company. The company then takes necessary action before releasing the software worldwide.

c) Operational acceptance testing (OAT)

Operational acceptance testing of the system is performed by operations or system administration staff in the production environment. The purpose of operational acceptance testing is to make sure that the system administrators can keep the system working properly for the users in a real-time environment.

The focus of the OAT is on the following points:

  • Testing of backup and restore.
  • Installing, uninstalling, upgrading software.
  • The recovery process in case of natural disaster.
  • User management.
  • Maintenance of the software.

Non-Functional Testing

There are four main types of functional testing.

#1) Security Testing

It is a type of testing performed by a special team. Any hacking method can penetrate the system.

Security Testing is done to check how the software, application, or website is secure from internal and/or external threats. This testing includes how much software is secure from malicious programs, viruses and how secure & strong the authorization and authentication processes are.

It also checks how software behaves for any hacker’s attack & malicious programs and how software is maintained for data security after such a hacker attack.

a) Penetration Testing

Penetration Testing or Pen testing is the type of security testing performed as an authorized cyberattack on the system to find out the weak points of the system in terms of security.

Pen testing is performed by outside contractors, generally known as ethical hackers. That is why it is also known as ethical hacking. Contractors perform different operations like SQL injection, URL manipulation, Privilege Elevation, session expiry, and provide reports to the organization.

Notes: Do not perform the Pen testing on your laptop/computer. Always take written permission to do pen tests.

#2) Performance Testing

Performance testing is testing of an application’s stability and response time by applying load.

The word stability means the ability of the application to withstand in the presence of load. Response time is how quickly an application is available to users. Performance testing is done with the help of tools. Loader.IO, JMeter, LoadRunner, etc. are good tools available in the market.

a) Load testing

Load testing is testing of an application’s stability and response time by applying load, which is equal to or less than the designed number of users for an application.

For example, your application handles 100 users at a time with a response time of 3 seconds, then load testing can be done by applying a load of the maximum of 100 or less than 100 users. The goal is to verify that the application is responding within 3 seconds for all the users.

Further Reading => Software Testing: A Comprehensive Guide

b) Stress Testing

Stress testing is testing an application’s stability and response time by applying load, which is more than the designed number of users for an application.

For example, your application handles 1000 users at a time with a response time of 4 seconds, then stress testing can be done by applying a load of more than 1000 users. Test the application with 1100,1200,1300 users and notice the response time. The goal is to verify the stability of an application under stress.

c) Scalability Testing

Scalability testing is testing an application’s stability and response time by applying load, which is more than the designed number of users for an application.

For example, your application handles 1000 users at a time with a response time of 2 seconds, then scalability testing can be done by applying a load of more than 1000 users and gradually increasing the number of users to find out where exactly my application is crashing.

Let’s say my application is giving response time as follows:

  •  1000 users -2 sec
  •  1400 users -2 sec
  •  4000 users -3 sec
  •  5000 users -45 sec
  •  5150 users- crash – This is the point that needs to identify in scalability testing

d) Volume testing (flood testing)

Volume testing is testing an application’s stability and response time by transferring a large volume of data to the database. Basically, it tests the capacity of the database to handle the data.

e) Endurance Testing (Soak Testing)

Endurance testing is testing an application’s stability and response time by applying load continuously for a longer period to verify that the application is working fine.

For example, car companies soak testing to verify that users can drive cars continuously for hours without any problem.

#3) Usability Testing

Usability testing is testing an application from the user’s perspective to check the look and feel and user-friendliness.

For example, there is a mobile app for stock trading, and a tester is performing usability testing. Testers can check the scenario like if the mobile app is easy to operate with one hand or not, scroll bar should be vertical, background color of the app should be black and price of and stock is displayed in red or green color.

The main idea of usability testing of this kind of app is that as soon as the user opens the app, the user should get a glance at the market.

a) Exploratory testing

Exploratory Testing is informal testing performed by the testing team. The objective of this testing is to explore the application and look for defects that exist in the application. Testers use the knowledge of the business domain to test the application. Test charters are used to guide the exploratory testing.

b) Cross browser testing

Cross browser testing is testing an application on different browsers, operating systems, mobile devices to see look and feel and performance.

Why do we need cross-browser testing? The answer is different users use different operating systems, different browsers, and different mobile devices. The goal of the company is to get a good user experience regardless of those devices.

Browser stack provides all the versions of all the browsers and all mobile devices to test the application. For learning purposes, it is good to take the free trial given by browser stack for a few days.

c) Accessibility Testing

The aim of Accessibility Testing is to determine whether the software or application is accessible for disabled people or not.

Here, disability means deafness, color blindness, mentally disabled, blind, old age, and other disabled groups. Various checks are performed, such as font size for visually disabled, color and contrast for color blindness, etc.

#4) Compatibility testing

This is a testing type in which it validates how software behaves and runs in a different environment, web servers, hardware, and network environment.

Compatibility testing ensures that software can run on different configuration, different databases, different browsers, and their versions. The testing team performs compatibility testing.

Other Types of Testing

Ad-hoc Testing

The name itself suggests that this testing is performed on an ad-hoc basis, i.e., with no reference to the test case and also without any plan or documentation in place for this type of testing.

The objective of this testing is to find the defects and break the application by executing any flow of the application or any random functionality.

Ad-hoc testing is an informal way of finding defects and can be performed by anyone in the project. It is difficult to identify defects without a test case, but sometimes it is possible that defects found during ad-hoc testing might not have been identified using the existing test cases.

Back-end Testing

Whenever an input or data is entered on the front-end application, it is stored in the database and the testing of such database is known as Database Testing or Backend Testing.

There are different databases like SQL Server, MySQL, Oracle, etc. Database Testing involves testing of table structure, schema, stored procedure, data structure, and so on. In Back-end Testing, GUI is not involved, the testers are directly connected to the database with proper access and testers can easily verify data by running a few queries on the database.

There can be issues identified like data loss, deadlock, data corruption, etc during this back-end testing and these issues are critical to fixing before the system goes live into the production environment.

Browser Compatibility Testing

This is a sub-type of Compatibility Testing (which is explained below) and is performed by the testing team.

Browser Compatibility Testing is performed for web applications and ensures that the software can run with a combination of different browsers and operating systems. This type of testing also validates whether a web application runs on all versions of all browsers or not.

Backward Compatibility Testing

It is a type of testing that validates whether the newly developed software or updated software works well with the older version of the environment or not.

Backward Compatibility Testing checks whether the new version of the software works properly with the file format created by an older version of the software. It also works well with data tables, data files, and data structures created by the older version of that software. If any of the software is updated, then it should work well on top of the previous version of that software.

Black Box Testing

Internal system design is not considered in this type of testing. Tests are based on the requirements and functionality.

Detailed information about the advantages, disadvantages, and types of Black Box testing can be found here.

Boundary Value Testing

This type of testing checks the behavior of the application at the boundary level.

Boundary Value Testing is performed to check if defects exist at boundary values. Boundary Value Testing is used for testing a different range of numbers. There is an upper and lower boundary for each range and testing is performed on these boundary values.

If testing requires a test range of numbers from 1 to 500, then Boundary Value Testing is performed on values at 0, 1, 2, 499, 500, and 501.

Branch Testing

This is also known as Branch coverage or decision coverage testing. It is a type of white box testing performed at the unit test level. It is done to make sure that each possible path from the decision point is executed at least once for 100% of test coverage.

Example:

Read number A, B
If (A>B) then
Print(“A is greater”)
Else
Print(“B is greater”)

Here, there are two branches, one for if and the other for else. For 100% coverage, we need 2 test cases with different values of A and B.

Test case 1: A=10, B=5 It will cover the if branch.

Test case 2: A=7, B=15 It will cover the else branch.

Comparison Testing

Comparison of a product’s strengths and weaknesses with its previous versions or other similar products is termed Comparison Testing.

Equivalence Partitioning

It is a testing technique and a type of Black Box Testing. During this Equivalence Partitioning, a set of groups are selected and a few values or numbers are picked up for testing. It is understood that all values from that group generate the same output.

The aim of this testing is to remove redundant test cases within a specific group that generate the same output but not any defect.

Suppose the application accepts values between -10 and +10, then using equivalence partitioning, the values picked for testing are zero, one positive value, and one negative value. So the Equivalence Partitioning for this testing is  -10 to -1, 0, and 1 to 10.

Example Testing

Example testing is real-time testing. It includes real-time scenarios and scenarios are based on the experience of the testers.

This type of testing is also known as experience-based testing because it uses the tester’s knowledge of how the application has worked in the past, how to break the application, what kind of errors are common in this type of application.

Graphical User Interface (GUI) Testing

The objective of this GUI Testing is to validate the GUI as per the business requirement. The expected GUI of the application is mentioned in the Detailed Design Document and GUI mockup screens.

GUI Testing includes the size of the buttons and input fields present on the screen, alignment of all text, tables, and content in the tables.

It also validates the menu of the application. After selecting different menu and menu items, it validates that the page does not fluctuate, and the alignment remains the same after hovering the mouse on the menu or sub-menu.

Incremental Integration Testing

Incremental Integration Testing is a Bottom-up approach for testing, i.e continuous testing of an application when new functionality is added.

Application functionality and modules should be independent enough to test separately. This is done by programmers or by testers.

Install/Uninstall Testing

Installation testing is performed to check that the software application is installed properly and working as per expectation. Installation testing is a phase of testing before users interact with the actual application for the first time. Installation testing is also called “Implementation Testing”.

Uninstallation Testing is performed to confirm if all the components or elements of the software are removed from the system or not.

Installation and Uninstallation Testing is done on full, partial, or upgraded install/uninstall processes on different operating systems under different hardware or software environments.

Mutation Testing

Mutation Testing is a type of white box testing in which the source code of one program is changed and verifies whether the existing test cases can identify these defects in the system.

The change in the program source code is very minimal, so it does not impact the entire application, only the specific area having the impact and the related test cases should be able to identify those errors in the system.

Negative Testing

The mindset of the tester is to “Break the System/Application” and it is achieved through Negative Testing.

Negative Testing technique is performed using incorrect data, invalid data, or input. It validates if the system throws an error of invalid input and behaves as expected.

It should not take much time to load any page or system and should be sustained during peak load. Different performance and load tools are used to do this testing.

Recovery Testing

It is a type of testing that validates how well the application or system recovers from crashes or disasters.

Recovery Testing determines if the system can continue its operation after a disaster. Assume that the application is receiving data through a network cable and suddenly that network cable has been unplugged.

Sometime later, plug in the network cable; then the system should start receiving data from where it lost the connection due to the network cable being unplugged.

Regression Testing

Regression testing is testing of unchanged features of the application to make sure that any bug fixes, adding new features, deleting, or updating existing features, are not impacting the working application.

To find out regression scope is an important part in  Regression Testing. To find out regression scope, Tester needs to find out the area of application where changes happened and the Impact of those changes on the entire application. It is difficult to cover the whole regression test suite in every release, so Automation Testing Tools are used in regression testing.

Risk-Based Testing (RBT)

For Risk-Based Testing, the functionalities or requirements are tested based on their priority. Risk-Based Testing includes testing of highly critical functionality, which has the highest impact on business and in which the probability of failure is very high.

Priority decisions are based on business needs, so once priority is set for all functionalities, then high priority functionality or test cases are executed first, followed by medium and then low priority functionalities.

Low priority functionality may be tested or not tested based on the available time. Risk-Based Testing is carried out if there is insufficient time available to test the entire software and the software needs to be implemented on time without any delay.

This approach is followed only by the discussion and approval of the client and senior management of the organization.

Static Testing

Static Testing is a type of testing which is done without the execution of any code. Reviews, walkthroughs, and inspections are different methods of performing static testing. Activities like reviewing of requirement documents, customer requirement specification, high level, and low-level design, code syntax, naming standards, etc. come under static testing.

Static Testing also applies to test cases, test plans, test scenarios. Static testing is done to prevent the defect rather than catching the defect at a later stage. That is why static testing is cost-effective.

For example, Tester is testing a pet insurance website. The logic for premium calculation is described in requirement documentation. As a part of static testing, testers can review the developer code for premium calculation and compare it with the requirement document to prevent the defect related to premium calculation.

Vulnerability Testing

The testing, which involves identifying weaknesses in the software, hardware, and network, is known as Vulnerability Testing. In malicious programs, the hacker can take control of the system, if it is vulnerable to such kinds of attacks, viruses, and worms.

We need to check if those systems undergo Vulnerability Testing before production. It may identify critical defects and flaws in security.

Recommended reading =>>  Pilot Testing – A Complete Guide

Conclusion

The above-mentioned Software Testing Types are just a part of testing.

However, there is still a list of over 100+ types of testing, but we do not use all testing types in all types of projects. Hence, we have covered some common Types of Software Testing which are mostly used in the testing life cycle.

Suggested reading => Prototype Testing Tutorial

Also, there are alternative definitions or processes used in different organizations, but the basic concept is the same everywhere. These testing types, processes, and their implementation methods keep changing as and when the project, requirements, and scope change.

Was this helpful?

Thanks for your feedback!

Recommended Reading

  • Alpha Versus Beta Testing

    Alpha and Beta testing are Customer Validation methodologies (Acceptance Testing types) that help in building confidence to launch the product and thereby result in the success of the product in the market. Even though they both rely on real users and different team feedback, they are driven by distinct processes,…

  • Which Software Testing Institute Should I join_

    The software testing question and answer posts are back! Yes, this post is part of Question and Answer Series we started couple of months back and I will be doing it frequently in coming posts. Today I am going to answer two questions 1) Which Software Testing Institute Should I…

  • Functional Testing Vs Non-Functional Testing

    Know the Difference Between Functional Testing Vs Non-Functional Testing with Examples: Software Testing is broadly categorized into Functional and Non- Functional Testing. Let us discuss in detail about these testing types along with the exact differences between both functional and non-functional tests. What is Functional Testing? Functional testing is testing the…

  • Build Verification Testing (BVT Testing)

    Build Verification test is a set of tests run on every new build to verify that build is testable before it is released to test team for further testing. These test cases are core functionality test cases that ensure application is stable and can be tested thoroughly. Typically BVT process…

  • Client-server and web based testing (1)

    An extensive analysis of Client Server Testing, Web Testing & Desktop Testing with Pros and Cons. Get to know how to test these types of applications with simple examples: This tutorial will give you the answers to the above questions in detail along with simple examples for your easy understanding.…

  • Manual Testing Tutorials

    Here is the complete software testing guide with 100+ Manual Testing Tutorials covering Testing Definitions, Types, Methods, and Processes. What is Software Testing? Software testing is a process of verifying and validating the functionality of an application to find whether it satisfies the specified requirements. It is the process of…

  • Software Installation and Uninstallation Testing Guide (1)

    Have you performed Software Installation Testing? How was the experience? Well, Installation Testing (Implementation Testing) is quite an interesting part of the Software Testing Life Cycle. Installation Testing is like introducing a guest to your home. The new guest should be properly introduced to all the family members in order…

  • an overview of functional testing

    This is an In-Depth Comprehensive Functional Testing Tutorial with Types, Techniques, and Examples. Let's begin.  Let us first understand what Functional Testing is? Functional testing is a kind of black-box testing that is performed to confirm that the functionality of an application or system is behaving as expected.  This is…


579 thoughts on “Types of Software Testing: Different Testing Types with Details”

  1. I am from non-tech Background. I want to join software testing field. Should i join testing or not? If i’ll do any testing certification, would that be helpful for me to start career as a s/w tester.

    Reply
  2. We have to perform smoke test before move to production.

    Ensure that application is working fine according to clients requairements. Checking Links and major functionality of the application.

    Reply
  3. You first need to decide is the area of software development is the one you like or is it software testing? That is the first decision you need to make.

    Now, as a fresher it would be a good idea for you to try different areas of the development cycle including development, testing, etc. In my opinion some of the most valuable areas is the one where you do requirements engineering – that is develepment, management, analysis, etc. Again, it is up to what you really want to take your career. Software testing will not stop, maybe there is a shift onto some new target areas as is softwar as a service (SaaS). If you like, write with more details to: Carlos.Ferrer@donegal.net and I can guide you better. .net is also promising but keep in mind that you will be developing for windows based applications as opposed to Java where you can write software OS independent.

    Whatever the route you want to take, there are ways to be good and go up. For example after manual testing you can go into software test automation, etc.

    Best of luck

    Carlos Ferrer @ Waterloo, Ontario, Canada

    Reply
  4. hi. their
    i m 2009 batch passout graduate from electronics & instrumentation field. Also done a VLSI design course from CDAC. But now i m planning to do a testing course, please let me know is this will beneficial for me to do??
    can’t a person who is from instrumentation background do this course??
    is it restricted for core software persons only??
    is this course requires good knowledge of core software subjects like java,C# n all.
    please help me out

    Reply
  5. hi..
    i am trying to join in testing course. Is there any different courses in testing? If yes then which would be the better course??
    Plz give me rply

    Reply
  6. hi manjula,
    i guess we need to do a system restore. Is this your personal computer or office computer.
    I cant type the steps here, since it going to take some space of the blog. so respecting that. i will e-mail you the steps.

    Regards,
    Tiger2K

    Reply
  7. what is Bug Eye Testing?
    Since there is more monitoring tools why there is need of performance testing tool…even if the other tools monitor the application or software or any device pls reply me???

    Reply
  8. sir, i am doing project in software testing ,can u send me …what r the fields where we use software testing. i mean aera…..

    Reply
  9. validation and verification in software testing?

    Validation is nothing but QC or Dynamic Testing.
    Once we get build form the dev team we should execute the test cases and validate the results this is called Validation.

    Verification is nothing but walkthrough/Inspection
    i.e QA/Static Testing.

    Verify wether we are doing write or wrong PCDA

    Plan-Do-Check-Act

    Plan and Do comes under Verification

    Check and Act comes under Validation.

    Reply
  10. Hi Vijay!

    Thanks for this valuable information. By the way, do you happen to work with OBI? It happens that there’s also a Vijay that I know there, a developer. Just curious.

    Regards!

    Reply
  11. Guys inregard of #244, so many are viewing the comments but no one replying my question…my question may be very silly for professionals but kindly clarify as those question were put to me in many interviews.

    Reply
  12. Hey Madhav,
    Yes you can use load runner to test java and .net applications.
    Load runner works fine on windows or unix,
    however i am not sure about linux. will check and let you know.

    Regards,
    Tiger2K

    Reply
  13. hello
    actually i have seminar on thursday i.e, on 23-07-2009.
    the topic was “how to design software and types of software design”.
    can you please send me the matter related to this topic.
    then i will take printouts from that.
    so please send it by wednesday.
    awaiting for your mail.

    Reply
  14. I really amazed to know that there are So many types of testing. Thanks for sharing ur information on Software testing.

    Reply
  15. Hi Manjula,
    Can you please forward the address of the interview which you attended to the person in the blog call ” Hi”.

    Regards,
    Tiger2K

    Vijay i hope i am not breaking the norms of this blog. if so pls let me know. i like this forum and i like to contribute. so just trying to help a fellow mates here.

    Reply
  16. Hello All
    I m Aditi i done my Bsc(Maths) on 2004 resently i done mcm but i have a backlock and i have 2 years gap
    bet Bsc and Mcm after mcm i done SQT from pune now i m searching job in s/w testing can i get job on this basis or plz tell me site of job information from pune
    thanks

    Reply
  17. hi I have done MSc.IT. in 2002 and also done a course of manual testing but I don’t have any work experience .Can I get a job in testing ? what should I do for that?

    Reply
  18. hi vijay sir,
    it is very helpful site for fresh/experienced software tester, i get job for manual testing, will you please provide full details about manual testing, types of bugtrackers used in manual testing, what are the main duties of manual tester, please help me…..

    Reply
  19. hai ,
    This my question.Plz reply answer for this.

    Typically, if we know the basic knowledge for testing means that knowledge enough for all kinds software testing.

    Reply
  20. Dear Ms. Ameya (#257),
    Let y(our) organization uses whatever model.
    Just disclose the same model what you are using/following. Just make sure that, You are aware of which type of integration (big bang/ incremental/ top-down/ bottom-up) you are following in your Incremental Model.

    If you are forced to answer about STLC, Just explain testing process flow, Like when you start testing, when you end testing, I mean, Give a clear picture about testing process carried out in your organization.

    Regards,
    Govardhan Reddy M,
    Software Test Engineer.
    “Law of win says, Lets not do it in my way or your way, But lets do it in the best way”.

    Reply
  21. I am also searching for a job in Testing field. Even i don’t have real experience. Can u please give me suggestion without experience how can i get a job in testing. Recently i got h1 visa. I am So tensed. Whether I can face the interview or not?

    Reply
  22. hi sandeep
    Grey testing involved both white or glass testing and black testin.
    Black box testing also known as functional testing.
    White Box testing also known as structure test or glass testing

    Reply
  23. SOFTWARE DEVELOPMENT USES SEVERAL TYPE OF TESTING TO ENSURE PROPER FUNCTIONALITY ,WHICH OF THE FOLLOWING TYPE OF TESTING IS USED TO TEST FUNCTIONALITY ON COMMERCIAL COMPLIED SOFTWARE?
    A.WHITE BOX TESTING
    B.BLACK BOX TESTING
    C.CODE REVIEW
    D.CRYSTEAL BOX TEST

    Reply
  24. Hi Darshini,
    Please mail across all your testing related question, i would be happy to help you. my reply may get delayed since i am currently in usa, so their is a time difference. but i will surely answer your question. whenever i get time.
    and remember one thing “NO QUESTION IS STUPID, IT JUST HELPS YOU LEARN MORE.”.

    Regards,
    Tiger2k
    lonegladiator@gmail.com

    Reply
  25. This information is very useful.

    I’m 30 year’s old, i have my own business related IT, now i want to switch my way. Anyone can tell me if i choose this software testing way is it correct or not?

    Someone told me there is no scope for software testing in future.

    Reply
  26. working as a test team supervisor for a software development company named ABC.inc. In your opinion unit testing is more appropriate for which testing technique among Project based testing and Product based testing.

    Reply
  27. THIS IS THE VALUEBLE INFORMATION BUT I WANT SOME IMPORTANT INFORMATION WHICH I CAN UNDERSTAND ABOUT SOFTWARE TESTING.

    Reply
  28. Simply want to say your article is as astonishing.
    The clarity in your post is simply great and i could assume you are an expert on
    this subject. Fine with your permission let me to grab
    your feed to keep updated with forthcoming post.
    Thanks a million and please keep up the rewarding work.

    Reply
  29. I like the article. Only issue I have is unit testing appears to be conflated with module testing and component testing.

    Reply
  30. Josephine,

    Explaining SDLCs in detail is just so much to write. I will suggest to look at them this way. There are Traditional methodologies and Non-Traditional. Among the traditional ones, we have, code and fix, spiral, waterfall, cleanroom, etc. Among the non-traditional or so called agile we have, RUP, Scrum, Crystal, Adaptive Software Development, and, FDD (Feature Driven Development), etc. None are perfect and I would decide on using them after an initial assessment of the future application. In other words, you may want to use the traditional ones when the requirements are clear and “good”, otherwise, an agile metholodogy would suit.

    Start learning the traditional ones, then the agile.

    Good luck

    Carlos Ferrer

    Research In Motion
    “The creators of the Blackberry”

    Reply
  31. Great point. Modern commercial apps are translated into multiple languages.
    We did about 13 different languages, including bi-directional (Hebrew and Arabic) and Indic and Asian languages.
    Whew! There’s a LOT to know dealing with those.

    Reply
  32. Hi STH,
    The article is well articulated.
    However, I may suggest a better segregation of Types of Testing, as certain ‘types’ mentioned above are more like ‘stages’ at which testing is conducted.
    e.g. System and Unit testing are Testing levels/stages, while Acceptance and Compatibility are Testing types.

    For my point of reference, please do give this Wiki page a look – https://en.wikipedia.org/wiki/Software_testing
    You can view the ‘Content’ box for a nice overview of what I mean.

    Reply
  33. Dear Mr. Deepak (#268),

    Sodtware Testing:
    ——————-
    Process of executing an application with the intent of finding bugs.
    Process of giving assurance to the client that, The software under test is performing as intended (meeting the requirements).

    Testing Types:

    Black box testing: testing carried out from users perspective (no code knowledge required)

    White box testing: testing carried out by developers (unit testing / component testing / code testing)

    Gray box testing: 50 % of black box & 50 % of white box

    Regards,
    Govardhan Reddy M,
    Software Test Engineer.
    “Law of win says, Lets not do it in my way or your way, But lets do it in the best way”.

    Reply
  34. Hi All,

    Here are the differences you can see,

    SMOKE TESTING:
    1) Smoke testing 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 fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
    2) A smoke test is scripted–either using a written set of tests or an automated test
    3) A Smoke test is designed to touch every part of the application in a cursory way. It’s is shallow and wide.
    4) Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification).
    5) Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

    SANITY TESTING:
    1) A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
    2) A sanity test is usually unscripted.
    3) A Sanity test is used to determine a small section of the application is still working after a minor change.
    4) Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
    5) sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

    Hope this helps…

    Regards,
    VijayD

    Reply
  35. They make fool students by lots of advertisement. Dont give job and teach nothing. I will not recommend Seed Infotech to anybody. Many student in one batch… what we can learn.. Its better to learn from any working person who teach testing rather Seed Infotech
    seed Infotech teach nothing . Many Companies black listed seed infotech
    must read URL [SEED INFOTECH IS ROBBING STUDENTS, DONT JOIN ]
    http://www.consumercomplaints.in/complaints/seed-infotech-is-robbing-students-dont-join-c393565.html

    Reply
  36. Hi phalguna
    Thanks for ur reply
    I need some extra info about db testing
    I know its like entering data in the outer interface and checking in the database
    but is it all that…???
    I heard its more than that…
    i need to perform it in my organization…
    I wanted to know wtelse other than the thing i mentioned will happen in db testing…

    Reply
  37. Above post is nice..
    But Iam totally confused with “difference between Testing Methodologies, Testing Techniques and Testing Types”
    pls any one can clarify my doubt..

    Reply
  38. Hi all, Iam new to this blog but i liked this site as it is very helpful.

    Iam new to testing i want to know when we start doing testing how can we know what type of testing is done at what time. i just want to know the whole process of testing in an organization
    Please help.

    Thanks in advance

    Reply
  39. @Sathis18 :
    Sanity testing is to make sure the product works in general.
    Regression test is to make sure there is no more issue which happened before.
    Normally, regresssion test will be done after a bug is fixed. Then, a sanity test will be done to make sure this bug fix will not make any side effecct on the overall function.

    Severity is the level defined by the symptom. i.e high severity as system will crash, function not available or low severity as some comics error. While priority is base on the business consideration. i.e. for STB, click speed forward button will be effective twice is not high priority issue. But, when doing MOD ordering, click Ok button will be effective twice will be high priority issue need to be fixed.

    Reply
  40. Hi I have done MSc. IT in 2002 .Also I have done a course of manual testing but I don’t have any work experience .Can I get a job in s/w testing ?How should I prepare for that?

    Reply
  41. We do Smoke testing to check whether the major functionality is working properly or not before the unit testing so that it will not throw major defect during testing.

    Installation is a process which is done after the acceptance testing.

    testing sequence is answered above.

    Reply
  42. Testing Polymorphism allows variables to have different types according to the structure of the inheritance hierarchy. It is one of the cornerstone features of object-oriented programming. The emphasis in object-oriented programs is on defining abstractions that have both state and behavior. This emphasis causes a shift in the focus from software units to the way software components are connected. Thus, we are finding that we need less emphasis on unit testing and more on integration testing. The compositional relationships of inheritance and aggregation, especially when combined with polymorphism, introduce new kinds of integration faults. Testing criteria are introduced that take the effects of inheritance and polymorphism into account based on the work on coupling-based testing criteria.

    Reply
  43. Testing is the unavoidable part of any responsible effort to develop a s/w system.optimism is the occupational hazard of programming,testing is the treatment.

    Reply
  44. Hi,
    m back to this page….
    This time with info on System testing because people seem to be confused….

    You may be asked question in interview about what is System testing ? or What is difference between Functional and System Testing ?

    Functional Testing –

    Everyone knows it… so I am not going to explain it in detail… to keep it short you test the functionality of the software or product during functional testing.

    All the features, transactions are checked in functional testing…
    The most common type of testing.

    System Testing –
    Like you must had read in above comments – it is the End to End type of testing.
    Ok… but what does it mean?

    You can test the software right after you login till you logout…. Test everything in between and system testing is done…. M just kidding … it’s not true….

    Then what is system testing….

    It means you check the system from all perspectives…. Check it functionally as well as non- functionally…

    Check the functionality by doing functional testing.
    Check the non-functional requirement like –
    Usability
    Accessibility
    Compatibility
    Localization
    Performance
    Ad-hoc etc..etc.. (I cannot recall rest of the types…)

    In short you are supposed to test everything (all kinds of testing) in System testing. That’s why it is called as end-to-end testing…

    One liner definition of system testing –
    To make it simple, system testing checks the functional as well as non-functional requirement of the software.

    Functional requirement affects the product directly (like its features etc…) whereas non-functional requirement will affect the product in-direclty (like page load time, its compatibility with different browsers, user friendliness, localization etc…). So it is important to check the non-functional requirement as well.

    Hope everyone is clear now…

    Lets make it simple…

    Cheers,
    Sameer K

    Reply
  45. Hi Vijay, Can you please tell how to understand crash logs of IOS apps , i know this is not related to testing, But when i attending interview they are asking for how do you understand crash logs.

    Reply
  46. hi everyone,
    am studying msc in IT and its my second semester. please let me know any website to refer my subject software quality and analysis. do help…

    Reply
  47. This is great Article and very helpful for the beginners like me. Please guide me in this field this is totally new field for me and i have to walk through this path.
    Please help me sir.

    Reply
  48. Hi Vijay,

    What is Testing Technique?
    Difference between Testing Technique, Testing Types, Testing Methodologies.
    Is Black & White box testing is Testing Technique or Type of testing.

    Please clarify me

    Reply
  49. Hi Meenu

    Can u please tell me what r the questions they ask in the interview. because i am also planning to attend the interviews. but i don’t have any experience. if u share your questions that is more help for me.

    Reply
  50. thnx a lot. it was really helpful reading this. as i m new in testing it will help in long run…..tell something about how to develop test cases. thnku..

    Reply
  51. hai Tiger
    Thanks a lot, if possible plz tell me about RTM and TRM and any more interview questions
    Waiting for replay
    Thanks and regards
    Prasad

    Reply
  52. dear friends
    i am M.Sc(Computer science).presently working as lecturer in CS. I interesting to working in programming and testing. For that, i shifter to present career to new field i.e stftware testing. i learing some thing in testing. please help me any fresher jon in testing.

    thanks all

    Reply
  53. Hii im a fresher i want to start my career in software field . I did many web-based Applications ….Am waiting for Good oppurtinity, please help me..

    Reply
  54. can anyone explain what is Test Stratergy and Test Plan? what is the difference between them? Also explain about Traceability Matrices?

    Reply
  55. st post 6 : Crash Test Dummy on 05.03.12 at 7:39 am

    […] Have you wondered how to add Adsense ad unit in post left or right corner in post content? This was my first question when I switched to wordpress. As you can see many wordpress blogs have ad units embedded in top left or right corner of the post content see example. […]

    Reply
  56. hai prashant katkar
    Test cases for Mobile Phone

    1)Chek whether Battery is inserted into mobile properly

    2)Chek Switch on/Switchoff of the Mobile

    3)Insert the sim into the phone n chek

    4)Add one user with name and phone number in Address book

    5)Chek the Incoming call

    6)chek the outgoing call

    7)send/receive messages for that mobile

    8)Chek all the numbers/Characters on the phone working fine by clicking on them..

    9)Remove the user from phone book n chek removed properly with name and phone number

    10)Chek whether Network working fine..

    11)If its GPRS enabled chek for the connectivity.

    Test Cases On Fan:
    1.It should have a hook for hanging in the roof.
    2. it should have minium three blades.
    3. If should be moving once the electricty pass into it.
    4. Speed of the fan should be controlled by the regulator.
    5.It should be stop once the electric switch off.
    6. The fan should run with minimum noise.
    7. The blades should have proper distance from the ceiling.
    8. The fan while in motion, should not vibrate.
    9. The color of the fan should be dark.

    Reply
  57. Hi Manjula,

    CMM means Capability Maturity model,Its a methodology used to refine and improve software developement process in a software company.
    Their are 5 levels of CMM. Any companies which practices the rules will be called as a CMM level company. Once again depending on the level which the follow. They will be certified.
    CMM is a thing of past it has been successfuly replaced by CMMI ( Capability Maturity model integration).

    Regards,
    Tiger2K

    Reply
  58. Hey Madav,
    Yes madav. You can use loadrunner to test .net and java applications.
    Load runner supports windows and unix, however i have my doubts on linux.

    Reply
  59. Thanks for the information, Vijay. It is very useful. Very well written!

    Sameer, nice explanation of difference between sanity test and Smoke test.

    Reply
  60. Hi Aruna,

    Every testing team conducts planned testing, but sometimes testing team adopts informal testing, due to some challenges or risks.
    For Eg: Lack of time, lack of resources, lack of team size, lack of skill, etc…
    This informal testing is also known as Ad-hoc testing.

    Reply
  61. what is the testing tool that support :
    1-Penetration- Failover – Stress testing types
    2-No. of users: Virtual users (200 concurrent user) “Assumption Reference #RFP ”
    3-Technology:
    -HTML 5
    -Java
    -Java Script
    -Oracle BPM suite
    -Oracle Business Intelligence Enterprise Edition
    -Oracle Siebel CRM
    -Oracle Web Center

    Reply
  62. Nice to have definitions of the different types of Software Tesing at one place. It makes easier to recall so many Testing related concepts. Thank you.

    Reply
  63. THanks. Nice article. really helpful.

    Suggestion:
    Please move comments box on top of all comments. web users have to scroll all the way down to write comments. 🙂

    Reply
  64. Greetings,
    I am a Ph.D. student in CS just got accepted in an IT company as a tester, your blog is like a goldmine to me but what I noticed is that all the information are focused on software testing, how about websites and web application testing I really hope to see that in your blog thanks.

    Reply
  65. I think everything said was actually very reasonable.
    However, what about this? suppose you composed a catchier post title?
    I mean, I don’t wish to tell you how to run your blog,
    however what if you added something that grabbed folk’s
    attention? I mean Types of Software testing and definitions of
    testing terms — Software Testing Help is kinda plain. You should look at Yahoo’s home page and
    note how they write post headlines to get viewers interested.

    You might add a video or a related pic or two to grab readers excited about what you’ve
    written. In my opinion, it could make your website a little livelier.

    Reply
  66. Hello ankita……

    Below are the phases of STLC:

    1. Requirements phase
    2. Planning Phase
    3. Analysis phase
    4. Design Phase
    5. Implementation Phase
    6. Execution Phase
    7. Conclusion Phase
    8. Closure Phase

    If you have any problem then mail me id:-Ashok.burania@gmail.com

    Reply
  67. validation and verification in software testing?

    Validation is nothing but QC or Dynamic Testing.
    Once we get build form the dev team we should execute the test cases and validate the results this is called Validation.

    Verification is nothing but walkthrough/Inspection
    i.e QA/Static Testing.

    Verify wether we are doing write or wrong PCDA

    Plan-Check-Do-Act

    Plan and check comes under Verification

    Do and Act comes under Validation.

    Reply
  68. This article provide useful information, however, it mixes up, types of testing, test levels and testing techniques. While these are related it is important to know and understand the differences.

    Reply
  69. “Software Testing Types:

    Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.

    White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions”

    Saloni, but here they mentioned Black & White box testing as type of testing?

    Reply
  70. Hi,

    Can anyone help me out in stating what are the different test scenarios will be covered in system testing and functional testing.

    I was aksed this in aninterview

    Reply
  71. i have completed MCA and i m a fresher.. i have done fast track course on software testing. your suggestions have helped me a lot. tahnx

    Reply
  72. really, this is very helpful and easy to understand, thanks to them who posted this……………………….

    Reply
  73. Hi guys i have a question??
    1. what is the difference between Beta testing and Gamma testing??
    2. Give distinguishing factors between Black box and white bot testing..
    Thanks

    Reply
  74. @Vijay,
    In your article End to End testing is explained as wrong. The name itself will give the exact definition. Say for Example the ATM transaction, End to End testing is test to be performed from inserting a card to get cash, reciept, card. That means the entire functioniality of an application from the input to output is know as End To End Testing.
    Cheers
    george

    Reply
  75. Hi Renuka,

    This is Suresh Working as a Test Engineer. i have mentioned Regression Testing as given Below:

    What is Regression Testing?
    Introduction:

    This article attempts to take a close look at the process and techniques in Regression Testing.

    What is Regression Testing?

    If a piece of Software is modified for any reason testing needs to be done to ensure that it works as specified and that it has not negatively impacted any functionality that it offered previously. This is known as Regression Testing.

    Regression Testing attempts to verify:

    – That the application works as specified even after the changes/additions/modification were made to it

    – The original functionality continues to work as specified even after changes/additions/modification to the software application

    – The changes/additions/modification to the software application have not introduced any new bugs
    When is Regression Testing necessary?

    Regression Testing plays an important role in any Scenario where a change has been made to a previously tested software code. Regression Testing is hence an important aspect in various Software Methodologies where software changes enhancements occur frequently.

    Any Software Development Project is invariably faced with requests for changing Design, code, features or all of them.

    Some Development Methodologies embrace change.

    For example ‘Extreme Programming’ Methodology advocates applying small incremental changes to the system based on the end user feedback.

    Each change implies more Regression Testing needs to be done to ensure that the System meets the Project Goals.
    Why is Regression Testing important?

    Any Software change can cause existing functionality to break.
    Changes to a Software component could impact dependent Components.

    It is commonly observed that a Software fix could cause other bugs.

    All this affects the quality and reliability of the system. Hence Regression Testing, since it aims to verify all this, is very important.
    Making Regression Testing Cost Effective:

    Every time a change occurs one or more of the following scenarios may occur:
    – More Functionality may be added to the system
    – More complexity may be added to the system
    – New bugs may be introduced
    – New vulnerabilities may be introduced in the system
    – System may tend to become more and more fragile with each change

    After the change the new functionality may have to be tested along with all the original functionality.

    With each change Regression Testing could become more and more costly.

    To make the Regression Testing Cost Effective and yet ensure good coverage one or more of the following techniques may be applied:

    – Test Automation: If the Test cases are automated the test cases may be executed using scripts after each change is introduced in the system. The execution of test cases in this way helps eliminate oversight, human errors,. It may also result in faster and cheaper execution of Test cases. However there is cost involved in building the scripts.

    – Selective Testing: Some Teams choose execute the test cases selectively. They do not execute all the Test Cases during the Regression Testing. They test only what they decide is relevant. This helps reduce the Testing Time and Effort.
    Regression Testing – What to Test?

    Since Regression Testing tends to verify the software application after a change has been made everything that may be impacted by the change should be tested during Regression Testing. Generally the following areas are covered during Regression Testing:

    – Any functionality that was addressed by the change

    – Original Functionality of the system

    – Performance of the System after the change was introduced

    Regression Testing – How to Test?

    Like any other Testing Regression Testing Needs proper planning.
    For an Effective Regression Testing to be done the following ingredients are necessary:

    – Create a Regression Test Plan: Test Plan identified Focus Areas, Strategy, Test Entry and Exit Criteria. It can also outline Testing Prerequisites, Responsibilities, etc.

    – Create Test Cases: Test Cases that cover all the necessary areas are important. They describe what to Test, Steps needed to test, Inputs and Expected Outputs. Test Cases used for Regression Testing should specifically cover the functionality addressed by the change and all components affected by the change. The Regression Test case may also include the testing of the performance of the components and the application after the change(s) were done.

    – Defect Tracking: As in all other Testing Levels and Types It is important Defects are tracked systematically, otherwise it undermines the Testing Effort.

    Thanks,
    Suresh
    bsuresh7282@gmail.com

    Reply
  76. can anyone explain breifly definitions for
    1) Acid Testing
    2) Ramp Testing
    3) Bucket Testing
    Its important please, reply immideately.

    Reply
  77. Which testing types are most used in new Software are Existing Software (or) Importent testing types for after release Software.

    Reply
  78. Hi ,

    I found this website very useful and informative . Can Any one answer this question

    Ques- Is the time taken by server in retrieving the record from a table is directly proportional to total number of records in a that table?

    thanks,

    Rita Jain

    Reply
  79. Hi Vijay,

    I am a novice and want to know what do you mean by deployment ? I keep on hearing we are having deployment from managers and what does that imply … and they said some code fixes are going to be deployed … could you throw some light on this process

    Reply
  80. I have experience in manual testing but i want to learn autoamtion also. please let me know any material / ebooks so that i can learn and guidance from all of u in both testings always.

    Reply
  81. Hi Shreya,

    This is Suresh Working as a Test Engineer. i have mention Database Testing link as given Below:

    Data bas testing basically include the following.
    1)Data validity testing.
    2)Data Integritity testing
    3)Performance related to data base.
    4)Testing of Procedure,triggers and functions.
    for doing data validity testing you should be good in SQL queries
    For data integrity testing you should know about referintial integrity and different constraint.
    For performance related things you should have idea about the table structure and design.
    for testing Procedure triggers and functions you should be able to understand the same.

    http://www.agiledata.org/essays/databaseTesting.html

    Thanks,
    Suresh
    bsuresh7282@gmail.com

    Reply
  82. Good evening guys.. i wanna ask something, it’s about model based testing, it’s still blur for me.. what is model based testing.. ok we start with software testing, there is two type of testing which are functional n nonfunctional, functional is black box, white box n grey box.. what about model based testing, where can we categorized it??? if we numbered it, it look like
    1.1 Software testing
    1.2 Software testing types
    1.2.1 Functional
    1.2.1.1 Black box
    1.2.1.2 etc..
    1.2.2 Non Functional
    1.2.2.1 Usability
    1.2.2.2 etc..

    is it correct? if it is correct where can i put model based testing.. i read in one paper, they said that model based testing can be applied to black box n white box testing but the confusing thing is, what is model based testing?? it’s a techniques or what?

    please feel free to answer me, really it’s make me confused so much.. thanks guys..

    Reply
  83. Folks,
    Lot of people are asking difference between Smoke and Sanity testing. And the more info you get, more confused are you people becoming.

    Let’s make it simple …

    Difference between Smoke and Sanity –

    Smoke testing is done to verify that the build (to be tested) is done properly. (The build is a new / updated version of software). The motive is to check that the application build is working fine and does not crash.

    For example – say an application has following features – (say each feature has a page, so in this case there are 10 features; so its 10 pages)
    Login, Logout, Enter info, delete info, update info, Change address, search records, retire records, print form, generate reports etc…

    Here’s how you will Smoke Test it –
    Check that each of the pages is displayed properly and there are no broken links between pages.
    Check that the buttons on the pages are clickable (not disabled or hidden).
    Check that you can traverse back and forth between pages.
    Check that you can see the help section pages, legal and disclaimer section on the pages (outgoing links on the pages)
    Check the look and feel of the pages (fonts and user text boxes displayed properly and no broken images or cluttered text or font scramble) – this is optional check unless you see something that is unreadable
    Check that you are able to enter info into input boxes (no need to do any transactions; just check whether you are able to input text on the pages or not).

    Note that you are not required to do any transactions in Smoke test. In other words you are not testing the functionality of the application but the application build itself.

    Sanity Testing – is done to verify whether the new / updated build is functioning properly. (Note the difference – smoke checks the application build; sanity checks the build functionality at higher level.)

    Take the above example again – say an application has following features –
    Login, Logout, Enter info, delete info, update info, Change address, search records, retire records, print form, generate reports etc…

    Here’s how you will Sanity Test it –
    Check that the customer critical functionality is working by performing at least one transaction for each of the major features.

    Your depth of sanity testing depends on the functionality of the application. Say there are 5 major features of that application. So you need to perform only one transaction for each of the feature (to verify that all the major features are working properly).

    (Sanity test concentrates on testing major features. A feature is said to be major if it is accessed by customer frequently or daily and its working is important to the business. )

    Now say the login, logout, enter info, delete info and generate records are the 5 main features on the application.

    Sanity test –
    Check that you are able to login
    Check the you are able to logout
    Check the you are able to enter the info and save record for new user.
    Check that you are able to delete data of existing user.
    Check that you can generate report for current date.

    You don’t need to test rest of the features. Nor do you require to run other exhaustive test cases for each of these major features.

    Note that you just have to check that the basic functioning of the major features is working. Don’t run end to end and multiple operation test cases in sanity.
    Just ran the Basic test case for which that feature is designed.

    Hope that now everyone has got clear understanding of Smoke and Sanity testing. And the Difference as Well.

    Lets make it Simple…

    Cheers,
    Sameer K.

    Reply
  84. hi,
    Pls tell me….
    I am studying mca final year….I am intersting in Testing side. So what i do…? How to get a job in testing side…? What will i prepare…? What they want when i go Interview in testing job.

    Reply
  85. When an application is given for testing, with what initial condition the testing will be started and when are all the different types of testing done following the initial testing?

    Reply
  86. hai Tiger
    I am getting a Msg as “Failed to Install temporary license(error code 11) you need to install permanent license” when i tryed to install Qtp Through the link u have given

    Thanks and Regards
    Manjula

    Reply
  87. I completed my M.sc in Biochemistry(2003) ,Iam interested in software testing, I want to switch over to IT field,pls suggest me How can i? Eagerly waiting for reply.

    Reply
  88. Hi
    plz reply this question

    Is there any crowd testing technique of software testing?I have read about this technique in a paper written by Tarun vohra.

    Reply
  89. hi,

    I am finished mca this yr.i will interst study tesing course. it is useful for my future.wat abt tesing.then if i will study this course wat type of job will i search.pls give me reply.

    Reply
  90. Hi Govardhan,
    This is Mr. Ameya…Thanks for your comment but my company is using Incremental model and I am confused about STLC and phases of STLC.

    Reply
    • in Sanity Testing we check the main functionality are working fine. and re testing is like regression where we fix a bug and test whole application.
      Priority is where task Priority is high low or highest. where severity is where in application any page or unit is crashed. not working.

      Reply
    • hloo,

      sanity testing is also known as build version testing or build acceptance testing this is the first test conducted after every build release to ensure that any functional changes occurred

      re-testing is testing a functionality with different sets of data

      severity represents that impact of a bug on an application

      and priority represents that how important to fix a bug in an application

      Reply
      • Then what about smoke testing ?
        If both are similar,then plz tell me the core difference and the flow of testing.
        Thanks in Advance.

    • Sanity Testing Is Done By Tester After Accepting The Build
      1) Navigation Testing
      2) Installation Testing
      3) Proper Functionality Is Available Or Not.
      This All Point Came Under Sanity Testing.

      Retesting
      Test The Application With Different Set Of Data Called Retesting.

      Priority
      This Term Use By Developer For Major The Defect Strength
      Critical
      High
      Medium
      Low
      This Term Use By Tester For Major The Defect Strength
      Fatal
      Major
      Minor
      Suggestion

      Reply
    • Severity is how much the system is impacted and the priority is something that should be taken on first priorty

      Reply
  91. This is great Article and very helpful for the beginners like me. Please guide me in this field. This is totally new field for me and i have to walk through this path.
    Please help me sir.

    Reply
  92. Dear Mr.Anand (#220),
    Gray Box Testing means, 50% of white box testing and 50% of black box testing.

    Regards,
    Govardhan Reddy M,
    Software Test Engineer,
    “Get rid of anything that isn’t useful, beautiful or joyful”.

    Reply
  93. Hi, i started my career as developer c c++ and than I moved to testing as I have a passion for testing. Being from development back ground, unknowingly i have been contributing in development. I have no expertise in node.js. my pm wants me to have hands on experience. He is saying that will definitely help me grow in my career. I have started with api testing and created script using node.js. But I get satisfaction only in testing. My doubt is will backend knowledge will help me.I am good in both development and testing but testing is my passion and I feel I Am doing really well in it. My contribution is well recognised. Please suggest what I should do. Should I learn node.js or so I follow my passion

    Reply
    • If you pursue your passion, you will become very good at what you do, and you will enjoy your work regardless of your level of pay. If you enjoy your work, your expertise and dedication will lead to higher responsibilities and pay. Learning is never a waste of time. If you do not see why learning node.js will help you pursue your passion, then ask your PM he thinks it can help you. One clear potential is if you are testing node.js software, knowing the language of the developer is a big advantage.

      Reply
  94. Hello Friends,
    I will be very thankful if any one of you can give me any info regarding Witness Testing.

    Regards,
    Yogesh(Yogeshcsen@gmail.com)

    Reply
  95. hi tiger..
    is loadrunner a platform dependent. i mean can we do load testing on applications developed in java or dot net or any using loadrunner.

    Reply
  96. @Jay Bakshi You are correct
    All the types mentioned above are not testing types, Some of them are Types,Methods,Testing Levels etc.

    Reply
  97. As soon as the first build drop received by the test team, What all testing in stages is performed by Manual and Automation Engineer?

    Reply
  98. Hi to all, This is Venky. I am having some real-time doubts in software testing.
    What do you do in Sanity Testing?

    I have got a bug in my application. Then I reported it. But the developers are not accepting it as a bug. After so many negotiations they closed it as Deferred. But still I am feeling it as a bug. Because if the user uses it in such a way, definitely he will face the problem. But in the negotiations they said the user will not go in that way. What do I do now?

    Reply
  99. Hi Yamini,

    This is Suresh Working as a Test Engineer. i have mentioned Test Strategy as given Below:

    Test strategy:i hope that brief version of your test cases

    Test strategy is a company level document and which says
    the approch for testing.the test strategy doc also says
    that the scope,business issues,test delivarables,tools
    used ,risk analysis etc.

    Thanks,
    Suresh
    bsuresh7282@gmail.com

    Reply
  100. Hi friends,

    * The purpose of testing can be quality assurance, verification and validation.
    * The purpose of testing is to evaluate products to measure the results against the requirements, document the differences and help to resolve the differences.
    * The purpose of testing is to find bugs and make sure they get fixed.
    * To improve the quality of the product.

    Reply
  101. Thank u very much for assisting such a valuable help,,, i have my exam tomarow and i didn’t issued book from library, but your website helped me so much….

    Reply
  102. hi
    pls tell me the basic diff. between sanity & smoke testing
    also
    the diff between retesting & regression testing
    b’cos huge material is available on this
    & it make lot of confusion
    so i’ll expect right answer from u
    so
    thax in advance

    Reply
  103. @Prasad
    In both the contest you are testing the software that built as a whole.
    Testing Techniques for the both are same.
    But the Testing Process/Approach varies.
    Let me tell you in detail, the difference between the Application Dev and Product Dev.
    Applications were meant for the clients where as the Products for customers.
    We build application to fulfill the client needs(Specific to a particular client).
    Where as the products we design depending upon market needs to sell to many customer.

    Testing procedure varies depending upon the Development process and the quality adherences of the companies.
    Let me know if you need more information

    Reply
  104. Hi,

    I am preparing for testing interview.I had not done any testing course. Which type of soft skill important to join this field?

    Reply
  105. Dear Ms.Meenakshi (#230),
    Crowd Testing in software testing is max used in 3d objects (animations) more over using special type of automation tools (dedicated to only for doing crowd testing). In a word, We can discuss it as, Simulating more users (objects/agents/skeleton) etc., Means that making more/huge/high/big/heavy crowd with the already available (existing) crowd (object/….).

    A sample look can be viewed on the below link.

    http://www.crowdit.worldofpolygons.com/Examples.html

    This is to the best of my knowledge only.
    I don’t have any real time experience on this.

    Regards,
    Govardhan Reddy M,
    Software Test Engineer,
    “Law of win says, Lets not do it in my way or your way, But lets do it in the best way”.

    Reply
  106. hi
    I am fresher and and searching for job in software testing field. if anybody has any info about interviwes in this field plz tell me.

    Reply
  107. Dear All:

    I am a new blogger to this site. We shall circulate the clarification and get the info. on the testing ocean.
    All the best to everybody. Let us proceed with healthy discussions!!!

    – Saravanan S.

    Reply
  108. Hi,

    i am working as a tester in an MNC. Would like to be updated on various automation tools. Right now i am working in manual testing. Please give me some sugestions.

    Reply
  109. Black Box testing: testing without the knowledge of programing codes.
    Test case includes the requirement specification only.

    White Box testing: testing with the knowledge of codes/internal structure of software.
    Test case includes the requirement specification and internal codes.

    Reply
  110. With respect to the functionality of the appl. developers will develop the appl. and after development it comes to testing environment to start testing. in testing testers will do all phases of testing with intent of finding errors or like wise bugs and see that they are fixed properly………….

    Reply
  111. Hai,
    i am a beginner to software testing.can anyone please explain 1) what are the tools used for unit testing?
    2)unit testing is a mandatory testing done in all real time enviornment?

    Thanks

    Reply
  112. hai, this is very usful to all so plz read this and get a big brain in testing. by yours anandh. plz help me to give one job also for this answer

    Reply
  113. i want to make carrer in software testing so dats y i have done manual testing but jobs are still away from me…..plz suggest wat i do.

    Reply
  114. This section is really usefull for non-certified tester’s basically part time testers, so that they can get an idea of whtt testing actually means. thnks to the publisher

    Reply
  115. thanku,
    carlos ferror
    i choose .net , now i am in project, what sites we have for .net(help)
    in case of any assistance
    which site i have to see for help

    Reply
  116. can anyone tell me the sequence of the testing types performed in testing?
    Like
    1. Installation
    2. Smoke Testing…………

    Reply
  117. Hi shreya

    I have some idea about the database testing.In real time base supoose u will be testing Payroll System(Payslip). u wil enter the some data like as employee name ,basicsalary, empId ,etc…
    it’s outerface design .then u will enter the data base and check above data will be insert into database properly or not.some times data will be insert wrong manner why becase u will must check database every time.so module u will chek compare databse.

    Hope u have some idea
    plese replay

    Cheers
    PHALGUNA

    Reply
  118. Hi Vijay,

    This is Prathap from MBA(Finance) Background.

    I have plan to Join for testing course, I let me know which type of testing course is better for me & which one have good growth in future for MBA background students.

    Reply
  119. Dear Sandeep,
    Grey Box testing is a combination of white box and black box testing.
    Glass testing is purely white box testing.

    Regards,
    Sadiq

    Reply
  120. This information is very useful for all who wants to enter into testing field.
    Thanks alot for providing this information.
    I am also searching for a job in testing field in Boston.
    Now i am in H1 visa.i have done Msc .IT in chennai in the year 2002.
    Here Companies are looking for more Experienced persons with more skills in their resumes
    But i am not having any real time experience and am preparing through internet to attend interviews.
    So please give me suggestion that without having any experience how can i try for a job and tell me the sites which is more useful for me to learn easily

    Reply
  121. This section is very useful to me, and i am very interested to learn more about testing through software testing help. And i want more information about the automation testing like winrunner and load runner and qtp.

    Reply
  122. Hi All,

    This is Suresh Working as a Test Engineer. i have mentioned Difference between Load, Stress and Volume Testing as given Below:

    Load, Stress and Volume testing are the part of
    Performence testing.

    Load Testing: Load Testing gauges how efficently the
    application performs when its functions are tested with
    varying workloads.

    Stress Testing:Stress Testing looks to see how well the
    software reacts and compensates when resources are low.

    Volume Testing:Volume Testing tests the functional limits
    of the application by increasing the amount of data thrown
    at it untill it can no longer cope with the flow.

    Thanks,
    Suresh
    bsuresh7282@gmail.com

    Reply
  123. Hiii…. this is very useful information, bt can u plz describe stress, load, sanity, smoke testing in brief n in simple language??
    thanks a lot! abv information really helpful…
    can u do favour 4 me I am fresher and and looking for job in software testing field. if anybody has any info abt interviwes in testing plz let me know..

    Reply
  124. I am looking out for the testing job.My current exp is 2.1yrs in Manual Testing ( Functional Testing) . Kindly suggest me some companies where I can apply.

    Reply
  125. Hi Nazia. Here I am giving the answer for your Question.

    Black Box Testing: Without knowing the internal content of the box checking the outer appearance and quality of the box. Due to this only the name comes like Black Box Testing.
    In software terms “Testing the Software without knowing the internal design of the application by keeping the Functionality in mind”.

    Reply
  126. can anyone tell about the “Testing Polymorphism in Object Oriented Systems for Improving software Quality” tell me what to do ,how to test and methodologys.

    Reply
  127. Comment/Question:

    At the beginning of this page ‘Unit Testing’ is listed as a subset of ‘Functional Testing’
    My understanding is, Unit and Functional Testing fall into two different ‘Categories’ of testing
    Unit Testing is associated with Clear Box Testing
    Functional Testing is associated with Black Box Testing
    And as such, Unit Testing will never be associated directly or identified as a subset of Functional Testing.

    My distinction is not meant to criticize but a request for clarification.
    I am writing an ATP and (again) relying on your website for help
    I have often visited this site over the years for guidance and direction

    Currently I am arm wrestling with my development team over the ‘industry standard’ definition of ‘unit testing’ as a Q/A requirement for our ISO compliant environment and do not want to muddy the waters by using an ambiguous definition in an ATP for a Black Box (or manual / functional test process).

    I do however appreciate the distinction between functionally testing in isolation of specific functional components of the application vs testing functional components in conjunction with other functional components of the Application (system testing).

    Any help is appreciated.

    Reply
  128. Hi ,
    Plz reply.this que?

    I am 2007 batch passout.I got job in testing..Now only am entered in organization side..How to do in practical level.

    Reply
  129. @anuradha

    Volume testing is testing the application with huge amts of data.Ex: Posting many payments to a bank….
    at end of for settlement system we will have huge amount of data ..

    SAVE BUTTON is not working means its a failure.

    Reply
  130. Thanks Namita, Actually I was planning to have detail description of all types but later thought that it will be a big mess in single post. I will take one type at a time for future posting.

    Reply
  131. hi everyone!

    happy to see this much doubts and clarifications going on.

    can anyone help me in this,,

    what are all the steps involved in Requirement phase?

    regards,
    kamalrajan.V

    Reply
  132. Hi Saravanan,

    reg: Smoke & Sanity test.

    Actually both are similar techniques that some company follows smoke and some sanity or both.

    Well both the techniques done before the actual testing starts

    Reply
  133. Hi Friends,

    Today i just attend one interview and I was asked with the below question.
    Q: You are asked to qualify 10000 tetevisions. What will be your testing approach? What are the different scenarios you will identify to test? What are the edge/negative cases? How long will you take to complete the testing?

    Could anyone pls suggest me the proper answer?

    Reply
  134. Hi,

    I Want to know about the meaning for thisTest strategy :Its a high level document, which defines the objectives of all test stages and techniques that you apply.

    Reply
  135. hi,
    i am new to testing ,just now i started learning ,the above is very useful to me,will u provide me complete proses of testing in brief.

    Reply
  136. hi everyone

    I want to switch in testing .so i want to know that which is the best institute of testing and how will start my career in testing.can anybody help me for this question .i will be obilige to you.

    Regards
    thanks

    Reply
  137. Show stopper is a bug or a crash in application, which literally makes it impossible for the tester to proceed further with testing of the application.
    This kind of bugs have to be fixed on top priority basis.

    Regards,
    Tiger2K

    Reply
  138. It is really nice and very useful information. I am new to testing but still I understood atleast basic things. Thanks for this info.

    Reply
  139. It is a very good artical for gaining knowledge about the differenet types of software testing.The matter is good enough to learn and understand.

    Reply
  140. I am looking out for the testing job.My current exp is 2.1yrs in Manual Testing ( Functional Testing) . Kindly suggest me some companies where I can apply (only in Mumbai )

    Reply
  141. Hi,
    Which category does “Business process testing” fall under? functional or non-functional?
    Also is it manual or automation testing?
    It would be of great help if you could give me more details on business process testing
    Thanks!

    Reply
  142. what is actual difference between whitebox testing and black box testing…?
    what is actual difference between alpha testing and beta testing…?

    Reply
  143. A test plan is the base line for all the testing activities
    A test plan addresses what to do? When to do? And how to do?
    Test planning assesses the software application risks and then develops a plan to determine if the software minimizes those risks
    Testers must understand the development methods and environment to effectively plan for testing
    The tester must understand the new and increased risks in order to evaluate the controls in computer applications
    The test plan should be focused on the identified risk
    An Ideal Test Plan should comprise of:

    Test Scope
    Test Objective
    Assumptions
    Risk Analysis
    Test Design
    Roles and Responsibilities
    Test Schedule & Resources
    Test Data Management
    Test Environment
    Communication Approach
    Test Tools

    Reply
  144. Hi vijay, i worked as a developer and now i moved to testing, whether it would be efficient to work in testing like how developers are working. i want to know about open source automation tools. Please help me in this i want to explore in testing

    Reply
  145. Hi folks,

    I have 1.6 years of exp in ETL and Manual Testing.
    I got married and relocated so I need to quit my job in 2014.
    Now I wanted to re-join again into Testing domain.
    Is there a good scope of getting into IT firm again with that exp and break in between?
    Kindly advise me on this. Thanks in advance.

    Reply
    • Yes.. it is possible and at this point of time early joiner is most preferred candidate.
      Just apply through career portal of Company and create naukri profile as well, both will work and you will get a job soon.

      Reply
      • hii
        I completed my training on manual testing from jaipur .
        now i want to go delhi for abest carrier point .
        kindly advice me on this. thanks in advance

  146. @ Naga Vishala – In this case developer might ask to bug reporter for more details about the bug and can make the status of bug as “Need more Info”

    @Thilak – The answer is NO! Think about development, If you have theoretical knowledge of any programming language say C++, can you write a program using this language? No, you must have some hands-on knowledge. If you have basic knowledge of software testing then it’s not enough for all testing types. You can gain more knowledge of each type using your basic knowledge.

    @ chengaiah – Functional testing is black box testing without considering the program structure. You verify the program using specification document. System testing is end to end application testing which includes whole application as one unit and generally tested for usability, functionality, performance, load.

    Reply
  147. hi
    iam complete the m.c.a in this year
    iam joining the testing course.now a days testing is importent or not?
    ***can any body tell about difference the regression testing&retesting with examples?

    Reply
  148. my question is : during the installation of QTP 9.2 i am getting an error message as “unable to install .net application”.due to this i am it is not possible for me to install QTP in my pC.pls if anyone knows the reason let me know………

    Reply
  149. Hi Nazia,

    Black box testing, also called functional testing and behavioral testing, focuses on
    determining whether or not a program does what it is supposed to do based on its
    functional requirements. Black box testing attempts to find errors in the external
    behavior of the code in the following categories:
    (1) incorrect or missing
    functionality
    (2) interface errors
    (3) errors in data structures used by interfaces
    (4)behavior or performance errors
    (5) initialization and termination errors. Through
    this testing, we can determine if the functions appear to work according to specifications.
    However, it is important to note that no amount of testing can unequivocally demonstrate
    the absence of errors and defects in your code.

    u want more ans pls contact me: dreamz1207@gmail.com

    Reply
  150. Hi Manjula,

    Have you been using qtp on this computer before.?
    if yes, then its going to be a long process. you need to make some changes in system registry.

    i will e-mail you the steps which you need to perform in system registry.

    Regards,
    Tiger2K

    Reply
  151. Hi Can anybody help me out with alpha and beta testing please???Vijay the article is great and pretty informative is well

    Thanks
    Bye
    Darshil

    Reply
  152. Hi Vijay,
    it would b more clear if these testing types are given in a sequence in which they are performed. i m looking forward to it.
    thanks

    Reply
  153. hai dude im 3rd yr student,enakku testing pathi no ideas plz yarukkavadhu easya purivaika mudiyumna plz help me,innum na project pannala so plz help me dudes.i need to submit my project in better submission plz dudes.

    Reply
  154. i am fresher i got the job in one company . now i have two opprtunites .net and testing(only mannual )
    which one i have to choose and if i choose testing(only mannual) . can i have good future.
    plz help me

    Reply
  155. @ Aruna

    Sanity testing is done on an updated version of a software i.e. after adding the changes to the software, to check if it functions in the desired way.
    One example for that would be : suppose there is a new service pack for a windows operating system, then it is tested first to check whether the operating system works as required even after applying the new service pack or does it fail in any aspect.

    Smoke testing is generally done immediately after the development phase is over. Its main aim is to find out that the software would provide its basic functionality and wouldnt crash completely, and to ensure that the software would be able to sustain the exhaustive list of test cases.

    Reply
  156. Hello, i need some understanding please. I am on considering an interest in software testing so i made some enquiry online. I found this topics or classes in software testing
    * ISTQB
    * SQL
    * SELEQUI
    Are these classes related or all that is needed in software testing and do they also cover your listed types of software tests in your website. An explicit explanation will be greatly appreciated. Thank you.

    Reply
  157. the provided information is really good and useful.
    can any one give the difference between system testing,functional testing and end-yo-end testing

    Reply
  158. Ohh my God! Manjula is geting so many Doubts that Tiger was unable to give answers also! So, i request other people also to contribute and clear off her doubts.

    Reply
  159. Thanks for the total information about the testing,But may i know that what are the soft wares are using for testing?
    pplz,anybody knows send your answer to my mail(naresh.parpudi@gmail.com)
    thaank u.

    Reply
  160. Sanity and smoke are similar, but if the testing is done at the developers place by the developer then it is is called as sanity, if the same testing done by the tester at the test environment it is known as smoke

    Reply
  161. Present i am working in software company .Temper data (tool)
    is use in our company it’s a open source tool it’s effective testing tool or not.plese tell me which the most effective tool evailble in open source.

    Reply
  162. ya i completely agree with George.
    System Testing can be called as end to end testing
    where in from the scratch of the application the entire functionality of the application is checked.Each and every part of the application is checked for ita proper functionality.
    In actual testing it is the final phase of testing where the entire application is tested again for its functionality prior to User Acceptance Testing.

    Reply
  163. Definitely u will get job, but the problem is company charge to client based experience so always they prefer experienced one

    Reply
  164. Hi shreya

    I have some idea about the database testing.In real time base supoose u will be testing Payroll System(Payslip). u wil enter the some data like as employee name ,basicsalary, empId ,etc…
    it’s outerface design .then u will enter the data base and check above data will be insert into database properly or not.some times data will be insert wrong manner why becase u will must check database every time.so module u will check compare databse.

    Hope u have some idea
    plese replay

    Cheers
    PHALGUNA

    Reply
  165. hai tiger

    annu@vaysinfotech this the mail id u can ask the person anu HR of this company

    thanks and regards
    Manjula

    Reply
  166. Dear Ms. Ameya (# 254),
    Just fix for only one of the model(s). I recommend you to go for V-Model. Simple. Just at the interviews tell that, We are following V-Model.

    Regards,
    Govardhan Reddy M,
    Software Test Engineer.
    “Results matter, Efforts wont”.

    Reply
  167. can any1 pls tell me the sequence of testing type we perform …like which testing is performed first n after that which one????

    pls help me out its urgent

    Reply
  168. Regression Testing is done, in large part, to ensure what has already been functioning properly in an application in the previous production release was not negatively-impacted by updates that were done to enhance the application to meet the requirements of the current release. I.E. when development violates that famous standard health professionals honor, “First Do No Harm”.

    Reply
  169. @SELVAM AND @SAMPATH

    test plan is high level doc mostly prepared by test lead which contains various infmtn like version,testing approaches,test strategies,prioritising the tests,test case design,approval for test cases,bug report generation,regression testing,release notes etc and test strategy is something like what we are gng to test? i.e, it’s a description of what is gng to be tested.

    Reply
  170. Can anyone explain difference between test and testing?
    I’m translating software testing related document and I’m very curious whether these 2 words have different definitions apparently .

    Reply
    • A “Test” can be either a thing (a list of steps) or an action in the future.

      A test is a list of steps to validate something.
      To (as in an action) test is to perform the list of steps to validate something (a test).

      You can Test something. As In: I will test that the banana is soft. The key part here is that you “will” do it. It is in the future.
      Testing is present tense of the action; as in: I am testing that the banana is soft by stepping on it.

      Testing is the act performing a Test – in present tense.

      To make a confusing sentence to illustrate the different ways you can use test and testing in the English language:
      William asked me to test if the banana is soft so I am testing that this banana is soft by using this test I found on the Internet: Step on it and if it squashes, it is soft.

      I’m sure there are many people way better at explaining it, but I hope that helped.

      Reply
    • any requirement which specifies what a system should do – functional

      any requirement which specifies how the system perform a certain function – non functional

      Reply
  171. Continued…

    The CMM defines five levels of software process maturity, based on an
    organization’s support for certain key process areas (KPAs).
    Level 1 (initial) describes an organization with an immature or undefined process.
    Level 2 (repeatable),
    Level 3 (defined),
    Level 4 (managed),
    and Level 5(optimizing), respectively, describe organizations with successively higher levels of software process maturity.

    Regards,
    Tiger2K

    Reply
  172. hai Tiger

    plz can u give any link for free trial version QTP 9.2 for downloading if possible
    Thanks and regards
    Manjula

    Reply
  173. if a target of 450 test case is assigned to a test engineer how he can finish and execute within a given time