Home > Manual Testing > Manual Testing Types

Manual Testing Types

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.

Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

End-to-end testing – Similar to system testing, involves testing of 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.

Sanity testing – Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.

Load testing – Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.

Performance testing – Term often used interchangeably with ’stress’ and ‘load’ testing. To check whether system meets performance requirements. Used different performance and load tools to do this.

Usability testing – User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.

Install/uninstall testing – Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.

Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security testing – Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access. Checked if system, database is safe from external attacks.

Compatibility testing – Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

Comparison testing – Comparison of product strengths and weaknesses with previous versions or other similar products.

Alpha testing – In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing.

Beta testing – Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.

Advertisements
  1. senthil
    January 30, 2008 at 8:59 am

    Exploratory Testing?
    Exploratory Testing is the simultaneous learning, creating and executing of test cases. In traditional methods the learning and test case creation is done ahead of time working from functional requirements.

    Exploratory testing is the non process oriented testing while exploring testing can be done simultaneously and here the test engineer have 0% knowledge over the functionality.

    • srikanth
      March 16, 2011 at 3:00 pm

      Hi senthil…how are you? my friend is also senthil…nice to meet you

  2. senthil
    January 30, 2008 at 9:04 am

    Retest?
    Retesting is the term given to tests that are re-done to prove that a defect has been resolved.
    Conformance Testing
    Verifying implementation conformance to industry standards. Producing tests for the behavior of an implementation to be sure it provides the portability, interoperability, and/or compatibility a standard defines.

  3. senthil.G
    February 18, 2008 at 10:28 am

    what is smoke testing?
    smoke is the initial level of testing effort to determine if the new software version is performing well enough for its major level of testing effort

  4. March 12, 2008 at 12:01 pm

    dffdf

  5. gayatri p
    May 28, 2008 at 10:54 am

    What is Dogfood Testing?

    It is a daily basis testing even when one is not actively working on developing or testing the product.This is known as “eating one’s dogfood”. Many bugs, usually user interface (UI) issues but also occasionally web standards bugs, are found by people using daily builds of the product while not actively looking for failures. A bug found using this technique which prevents the user of the product on a regular basis is called a “dogfood” bug and is usually given a very high priority.

    • May 15, 2012 at 1:15 pm

      Nice But that is some confuse your defin

  6. gayatri padhy
    May 28, 2008 at 10:55 am

    What is Tendorbox Testing?

    Tests are also run on a continuous basis on a system known as the tinderbox.This tests the absolute latest code base, and therefore is a good way of catching unexpected compile errors (code that works on one platform might not work on another) and major problems such as startup failures. There are no CSS tests currently being run on the tinderboxes, however this is a direction which will be worth pursuing in the future.

  7. June 25, 2008 at 1:30 pm

    What is positive and negative Testing?

    Positive Testing:
    It is done with actual testing parameter not with junk value.
    Negative Testing:
    It is basically done with junk data and see what output is coming.

  8. Hari
    July 21, 2008 at 12:59 pm

    basic guidance for beginners in software testing?

  9. Imdad
    August 25, 2008 at 1:10 pm

    what are the types of Black box testing?

  10. ashwini
    March 9, 2009 at 2:55 pm

    what are basic guidance for beginners in software testing?

  11. suprita
    February 11, 2011 at 4:33 pm

    i need job get one job

  12. srikanth
    March 16, 2011 at 2:59 pm

    Hi Senthil

  13. May 18, 2012 at 12:41 pm

    Difference between automation testing and selinion testing

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: