This winter holiday season, give a precious gift to your career by upgrading your skills. | Get Flat 15 - 20% OFF on All Courses | Save Today

[iqquestion id=74]

6 thoughts on “Manual Testing : Different Types Of Testing Discussion 2

  • karim

    !- UNIT testing :
    testing each unit to show that individual parts are correct in term of requirement and functionality.
    2- White box:
    testing internal logic and structure of the code.these are done by software developers.
    3- Black Box Testing :
    testing based on entering input into the software program through user interface and observing output.
    4- Functional testing.
    5- Manual testing:
    testing software manually. tester takes over the role of an end user and tests the software to identify any unexpected behavior or bugs.
    INTEGRATION TEST:
    testing combined parts of application to determine if they function correctly TOGETHER.
    REGRESSION TESTING:
    RE-TESTING ALL PREVIOUS TESTS PLUS TESTING THE NEW THINGS.
    Use ability TESTING:
    testing how easy is to use application.
    NON-FUNCTIONAL TESTING:
    testing the software from the requirement that are non-functional.
    SYSTEM TESTING:
    testing overall requirement and specification.
    SMOKE TESTING:
    tests if major functionality is working.
    PERFORMANCE TESTING.
    testing how well is application performs.
    LOAD TESTING:process of putting demand on a system or device and measuring its response. all of these are done by software tester.
    LOAD TESTING:
    process of putting demand on a system or device and measuring its response. all of these tests are done by software testers.
    USER ACCEPTANCE TESTING:
    ensures that the customer has accepted the
    software and is ready for their use. this test is done by end users.

  • Olubunmi Ogunsola

    1. Unit Testing — Only testing one specific unit of program, developers usually do it. 2. Integration Testing — Done by developers
    3. Functional(System)- figuring out the features, making sure they work.
    4. Performance Testing — To see if it functions under multiple users. How well it performs doing normal, expected tasks.
    5. Acceptance Testing(End Users) — Having random users log in and rate the program. Regression Testing — Ability to recheck things from a prior testing to make sure new aspects aren’t affected by old ones, vice versa
    6. Regression testing – Retesting the software after a defect has been fixed in order to make sure nothing has been affected.
    7. Load testing – testing to see how system responds to an abnormal load
    8. Integration – tests combined unit to see how they function together
    9. Unit testing – tests each unit separately to see that it functions properly
    10. White box – Focuses on the internal aspect of the system
    11. Black box – Only focuses on the input and the output. So if you push this button then this should happen

    – Tomiwa

  • collins

    Unit testing- testing each unit to see if each part works.
    functional testing- seeing if the featues(buttons wroks)
    acceptance testing- tested by the different users to see if it fits their needs
    Black box testing – input and output without knowing the code
    White Box- testing the code its self
    Load testing- when its use by many users how it responds

  • Jomon Elengical

    1. Testing is divided as manual or automated testing based on whether a tool is used to run the test.
    a) Manual testing: No tool is used. Examples are unit testing, integration testing, system testing and user acceptance testing.
    b)Automated: a tool is used to run scripts. Examples are regression testing, load, performance and stress testing.

    2. Based on whether internal structure of software is known to the tester , testing is divided into white box and black box testing.
    a) White box testing: internal structure of software is tested to make sure specifications are met. Unit testing, integration testing and regression testing are dynamic white box testing.
    b) Blackbox testing: Internal structure of software is not known to the tester. Types are system testing, usability testing, performance testing. In this test cases are designed using the functional specifications of the software. It attempts to find the external behavior of the code.

    3. Testing is also divided as functional and nonfunctional testing.
    a)Functional testing is testing done against business requirement. Examples are unit testing, smoke and sanity testing, white and black box testing, UAT system testing, regression testing.
    b)Non functional testing is testing the application against client’s performance requirement. Examples are load/performance testing, security testing and stress testing.

    Unit testing: is done using white box methodology. Unit testing is a method by which individual units of source code are tested to determine if they are fit for use. It is written and executed by software developers to make sure that code meets its design and requirements and behaves as expected. It helps find issues at early stage which helps in reducing the cost of bug fixes

    Integration testing: is where individual software modules are combined and tested as a group to determine if they function correctly. It is performed after unit testing and is performed by programmers or developers. It uses white box or black box methodology. Integration testing identifies problems that occur when units are combined. Its objective is to verify proper interfacing between modules that satisfy functional requirements. Three major types of integration testing are big bang integration testing, top down approach and bottom up approach.

    Regression testing: is performed to confirm that a recent program or code change has not adversely affected existing features and that the code changes does not have side effects on existing functionalities. Already executed test cases are re-executed to ensure existing functionalities work fine. It is required when there is a code change due to change in requirement and also after fixing bugs and performance issues.

    System testing: is testing the behavior of a complete and fully integrated software product based on SRS document. It should investigate both functional and non-functional requirements of the testing. Its purpose is not to find faults but to demonstrate performance. It is done by the development team and is performed after integration testing. It uses black box technique.

    Usability testing: It is done by testers using black box technique. It tests whether the application or product built is user friendly or not.

    Alpha testing: takes place at the developer’s site. Developers observe the users and note problems. Unit testing, integration testing and system testing when combined together is alpha testing. It is done by the in-house developers in the first phase and is handed over to the QA in he second phase for additional testing in an environment similar to the intended use.

    Beta testing: takes place at the customer’s site where a sample of intended audience tests the product. Customers test the product and send feedback to developers and the developer makes appropriate modifications. This is done after alpha testing. Beta testing helps resolve real user problems and ensure release of a higher quality application to the general public.

    User acceptance testing: done by the end users. It uses the black box technique. It is to verify that the system meets the user requirements. It is done after system testing.

    Performance testing: It is a type of non-functonal testing. It is done to test speed at which some aspect of system work under a particular workload, stability and scalability. It helps improve user experience on sites and web apps, increase revenue generated from websites and identify bottlenecks such as database configuration.

    Load testing: A load test is usually conducted to understand the behavior of the application under a specific expected load. Load testing is performed to determine a system’s behavior under both normal and at peak conditions. It is performed with the help of automated tools such as Load runner.

    Stress testing:It involves testing beyond normal operational capacity,. often to a breaking point. It includes taking away some resources or applying a load beyond the actual load limit and to identify the breaking point. Stress testing help identify an application’s weak points and shows how it behaves under extreme load conditions.It is performed by testing different scenarios such as shutdown or restart of network ports randomly, turning the database on or off and by running different processes that consume resources such as CPU, memory, server etc.

    Security testing: Security testing involves testing software in order to identify any flaws and gaps from security and vulnerability point of view. It ensures that software is according to all security regulations, ensures confidentiality, integrity, software data is secure against known and unknown vulnerabilities.

    – jyothi

  • Banksy

    Unit testing – For correct Coding

    Integration Testing -design phase testing

    System Testing – Testing the Software within the environment it will operate in as well as the requirements or SRS have been met.

    Acceptance Testing – Manual functionality test done by the user

  • Solomon Ayanaw Habtu

    System testing can be categorized as manual and automation testing. Where Manual testing is done by human itself to insert data analyse the output without the help of any automation software. Example User acceptance testing, system testing are mostly done manually. Manual testing takes place when new vision system is released, and when there is no clear and consistent data to test the system.

    Automation testing is done by the support of automation tools like loadrunner, to test system. Automation is good by the time when there is repetitive similar tests, large number of data, and when the system has critical for errors. Regression testing, Performance, load, stress testing are mostly done automation tools.

    Testing methods can be categorized as Black and whit box testing: Where black box and gray testing focuses on the input and the output of the system based on the user, and system requirements without having knowledge about how the system works. system testing, user acceptance testing are categorized here.

    White box testing is testing done on the actual code how it works, based on system requirements. Mostly done by developers and it also used to improve the code performance, to remove unnecessary codes. Unit testing is an example of white box testing

    Gray box testing: it is a mix of Black box and some White box, a tester have some level about the system can be at a design level of the system and system requirements. This testing is good for system testing and integration testing.

    Functional testing: testing to check the functionality of the system based on the user and business requirements and specification.

    the following are some of functional testing:
    Unit testing: mostly done by the developer to check the module is working based on the system requirement specification and system design. Checks whether or not the individual module fulfills the functionalities based on the requirement.

    Integration Testing: it is a testing technique to test how different modules react each other when they work together based on the system design and requirement specification. It is done by test team.

    Regression testing: To test the health of new functionality, bug fix is added into the system and to see the the health of the surrounding impact of these changes.

    System Testing: the over all testing of fully integrated system before move to the market or owner. It can be functional or non functional based on the requirement specification.

    Beta testing: is conducted by selected users or testers to check whether the system is working based on the requirement before it is given to the owner or user

    User Acceptance testing: it is done by the end user/ owner to grant that the system is working based on their requirement. This is the final stage of testing

    Non functional testing: to check how the system performs/works in different situation:
    performance: testing the response time of the system. done by loadranner
    Load Testing: who the system performance is when the load/number user, data amount increases to the system with in the limited level. It also helps to see the max load capacity of the system

    Stress testing: also called torch testing, to see how the system reacts when some resources are blocked from the system while the load increases on it beyond its capacity. For example requesting data while making off and on the database server, network on/off and so forth

    Security testing: show the system is secured based on security issues like grant, session, cookie, sql injection, cross site scripts, directory traversing, authentication, authorization.

Leave a Reply