Manual Testing Certification Training

[vc_row full_width=”stretch_row” css=”.vc_custom_1559286923229{background-color: #f6f6f7 !important;}”][vc_column width=”1/2″][vc_tta_accordion color=”peacoc” active_section=”1″][vc_tta_section title=”Introduction to Software Testing Life Cycle” tab_id=”1559286383409-ab730398-6c03″][vc_column_text]Learning Objectives – In this module, you will learn the fundamental testing concepts. You will also understand the typical Software Development Life Cycle (SDLC) and different types of models involved. The different types of activities required for implementing a SDLC will be covered in this module.

Topics – History of Testing, What is Testing, Why Testing is required, What is a Defect, Testing principles, Quality Assurance and Quality control, Scope of Testing, When Should Testing Occur, Testing Constraints, Roles of the Software Tester, Overview on SDLC, Different Life Cycle models, Overview on STLC, AGILE Testing, etc.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Test Planning” tab_id=”1559286522681-3bf94e12-e7b7″][vc_column_text]Learning Objectives – In this module, you will learn all about Test Management activities. You will also understand the roles and responsibilities of the SDLC developers and your involvement/Contribution in each activity.

Topics – Test Strategy, Test Planning, Customization of the Test Process, Overview on Budgeting, Scheduling, Configuration management, and Risk management.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Test Design” tab_id=”1561382593569-b1979b66-b066″][vc_column_text]Learning Objectives – In this module, you will learn to create Test Scenarios, develop Test cases, Identify appropriate test data. At the end of this module, you will be able to write test cases on your own for sample apps. Traceability Matrix helps to bridge the Test coverage gaps.

Topics – Test Scenarios, Test cases, Test Data, Difference between Test Case and Test Scenario, Creating Test Cases for sample application, What is Traceability Matrix[TM], Sample TM.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Test Techniques” tab_id=”1561382595833-dd54d407-26c0″][vc_column_text]Learning Objectives – In this module, you will learn the importance of Reviews in Testing, Why to Review and How to Review? Writing effective test cases is a skill for a good tester. This module will give you an in depth study to understand Dynamic Test Case Writing Technique For Maximum Coverage with minimum Test Cases.

Topics – Static Techniques: Importance of reviews in STLC, Review Activities, Roles and Responsibilities during Review. Dynamic Techniques: Specification-based or black-box techniques, Boundary Value Analysis, Decision Table Testing, Equivalence Partitioning. Experience-based techniques: Error Guessing, Exploratory Testing.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Levels & Types Of Testing” tab_id=”1561382597303-5168678c-55b9″][vc_column_text]Learning Objectives – In this module, you will understand the different Phases and types of Testing.

Topics – Levels of Testing: Unit Testing, Integration Testing, System Testing, User Acceptance Testing. Types of Testing: Regression Testing, Smoke Testing, Database Testing, Load Testing, Performance Testing, Compatibility Testing, Security Testing, Volume Testing, Stress Testing, Usability testing, Internationalization Testing, Localization Testing.[/vc_column_text][/vc_tta_section][vc_tta_section title=”How does quality control differ from quality assurance?” tab_id=”1584633471731-12521b26-a05f”][vc_column_text]

Quality Control Quality Assurance
Quality control is a product-oriented approach of running a program to determine if it has any defects, as well as making sure that the software meets all of the requirements put forth by the stakeholders Quality assurance is a process-oriented approach that focuses on making sure that the methods, techniques, and processes used to create quality deliverables are applied correctly.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What is Software Testing?” tab_id=”1584633472440-1bc86900-b0f6″][vc_column_text]Software Testing is a process used to identify the correctness, completeness and the quality of developed software. It includes a series of activities conducted with the intent of finding errors in software so that it could be corrected before the product is released to the market.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Why is Software Testing Required?” tab_id=”1584633473251-e88c33c9-48ed”][vc_column_text]Software testing is a mandatory process which guarantees that the software product is safe and good enough to be released to the market. Here are some compelling reasons to prove testing is needed:

  • It points out the defects and errors that were made during the development phases.
  • Reduces the coding cycles by identifying issues at the initial stage of the development.
  • Ensures that software application requires lower maintenance cost and results in more accurate, consistent and reliable results.
  • Testing ensures that the customer finds the organization reliable and their satisfaction in the application is maintained.
  • Makes sure that software is bug-free and quality of the product meets the market standard.
  • Ensures that the application doesn’t result in any failures.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What are the two main categories of software testing?” tab_id=”1584633475358-51611da9-ee0b”][vc_column_text]Software testing is a huge domain but it can be broadly categorized into two areas such as :

  • Manual Testing – Manual Testing is the oldest type of software testing where the testers manually execute test cases without using any test automation tools. It means the software application is tested manually by QA testers.
  • Automation Testing – Automation Testing is the process of using the assistance of tools, scripts, and software to perform test cases by repeating pre-defined actions. Test Automation focuses on replacing the manual human activity with systems or devices that enhance efficiency.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What exactly is quality control? Is it similar to Quality Assurance?” tab_id=”1584633476206-e862b4b0-8419″][vc_column_text]Quality control is a product-oriented approach of running a program to determine if it has any defects, as well as making sure that the software meets all of the requirements put forth by the stakeholders.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What different types of manual testing are there?” tab_id=”1584633476964-4138f4a3-7531″][vc_column_text]Different types of manual testing are;

    • Black Box Testing
    • White Box Testing
    • Unit Testing
    • System Testing
    • Integration Testing
    • Acceptance Testing

[/vc_column_text][/vc_tta_section][vc_tta_section title=”Explain the difference between alpha testing and beta testing.” tab_id=”1584633477939-4c7eb6b8-900d”][vc_column_text]Alpha Testing – It is a type of software testing performed to identify bugs before releasing the product to real users or to the public. Alpha Testing is a type of user acceptance testing.

Beta Testing – It is performed by real users of the software application in a real environment. Beta Testing is also a type of user acceptance testing.[/vc_column_text][/vc_tta_section][vc_tta_section title=” What are the different levels of manual testing?” tab_id=”1584633478842-5b272481-6bec”][vc_column_text]Four levels of manual testing are:

Unit testing – It is a way of testing the smallest piece of code referred to as a unit that can be logically isolated in a system. It is mainly focused on the functional correctness of the standalone module.

Integration Testing – It is a level of software testing where individual units are combined and tested to verify if they are working as they intend to when integrated. The main aim here is to test the interface between the modules.

System Testing – In system testing all the components of the software are tested as a whole in order to ensure that the overall product meets the requirements specified. There are dozens of types of system testing, including usability testing, regression testing, and functional testing.

User Acceptance Testing – The final level, acceptance testing, or UAT (user acceptance testing), determines whether or not the software is ready to be released.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What is a testbed in manual testing?” tab_id=”1584633479740-0797634c-59d4″][vc_column_text]The testbed is an environment configured for testing. It is an environment used for testing an application, including the hardware as well as any software needed to run the program to be tested. It consists of hardware, software, network configuration, an application under test, other related software.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Explain the procedure for manual testing?” tab_id=”1584633480749-fd7f6956-eccf”][vc_column_text]The manual testing process comprises the following steps:

  • Planning and Control
  • Analysis and Design
  • Implementation and Execution
  • Evaluating exit criteria and Reporting
  • Test Closure activities

[/vc_column_text][/vc_tta_section][/vc_tta_accordion][/vc_column][vc_column width=”1/2″][vc_tta_accordion color=”peacoc” active_section=”1″][vc_tta_section title=”Test Execution” tab_id=”1561382561432-7f73ef2a-cc67″][vc_column_text]Learning Objectives – In this module, you will understand the Entry & Exit Criteria for Test Execution and how to execute the developed test cases.

Topics – Overview on Build and Release, Release Notes, Pre QA Checklist, Entry and Exit criteria, Test Execution, Hands on.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Defect Management” tab_id=”1561382561455-654071d3-eb53″][vc_column_text]Learning Objectives – In this module, you will learn the difference between Defect Prevention and Discovery. You will understand the Life cycle of Defect and how to report a defect with all sufficient details. This module will enable you to log defects and provide hands on.

Topics – Defect Prevention, Defect Discovery, Defect Life Cycle, Severity and Priority, Overview on RCA, Hands on Identify and log Defects.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Reporting & Team Collaboration” tab_id=”1561382611424-56181e07-6453″][vc_column_text]Learning Objectives – You are responsible to keep the stakeholders informed about the progress of your Test activities periodically. In this module, you will learn to prepare status reports on Test case development, Test case Execution, Defect Status report, Test Closure Reports. Real time examples will be showcased for better understanding. You will also learn how to interact with various teams and mitigate challenges.

Topics – Test Status Reports, Test Closure Reports, Tester and Developer, Team Collaboration, Client Interaction, Onshore/Offshore Model, Mitigate current challenges.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Metrics & Measurement” tab_id=”1561382613753-7c9c9136-4ca1″][vc_column_text]Learning Objectives – In software Testing, it is much important to measure the quality, cost and effectiveness of the project in line with testing. In this module, you will learn what is Metrics and how to collate Metrics and measure the quality of testing in various aspects.

Topics – Overview on Metrics & Measurements, Benefits of Test Metrics, Metrics Life Cycle, Types of Test Metrics.[/vc_column_text][/vc_tta_section][vc_tta_section title=”Testing Tools & FAQs” tab_id=”1561382614729-6b63842b-62b1″][vc_column_text]Learning Objectives – In this module, you will learn the importance of Automation tools, overview of some tools like QTP & Selenium, benefits and usage of Quality center.

Topics –  Why Automation, Overview of different Automation Tools – QTP and Selenium, Overview on Quality Center, FAQs.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What is the test case?” tab_id=”1584633482044-2cbbf3bd-8ceb”][vc_column_text]A test case is a document which has a set of conditions or actions that are performed on the software application in order to verify the expected functionality of the feature.

Test cases describe a specific idea that is to be tested, without detailing the exact steps to be taken or data to be used. For example, in a test case, you document something like ‘Test if coupons can be applied on actual price‘.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What is API testing?” tab_id=”1584633482958-fcdae915-b6b2″][vc_column_text]API testing is a type of software testing where application programming interfaces (APIs) are tested to determine if they meet expectations for functionality, reliability, performance, and security. In simple terms, API testing is intended to reveal bugs, inconsistencies or deviations from the expected behavior of an API.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What’s the difference between verification and validation in testing?” tab_id=”1584633484692-d647e868-a553″][vc_column_text]

Verification  Validation
It is a static analysis technique. Here, testing is done without executing the code. Examples include – Reviews, Inspection, and walkthrough. It is a dynamic analysis technique where testing is done by executing the code. Examples include functional and non-functional testing techniques.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What’s the difference between a bug and a defect?” tab_id=”1584633485629-16ba94b8-c086″][vc_column_text]A bug is a just fault in the software that’s detected during testing time. A defect is a variance between expected results and actual results, detected by the developer after the product goes live.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What are the advantages of manual testing?” tab_id=”1584633486511-16ea05da-e6bf”][vc_column_text]Merits of manual testing are:

  • It is a cheaper way of testing when compared to automated testing
  • Analysis of product from the point of view of the end-user is possible only with manual testing
  • GUI testing can be done more accurately with the help of manual testing as visual accessibility and preferences are difficult to automate
  • East to learn for new people who have just entered into testing
  • It is highly suitable for short-term projects when test-scripts are not going to be repeated and reused for thousands of times
  • Best suited when the project is at early stages of its development
  • Highly reliable, since automated tests can contain errors and missed bugs

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What are the drawbacks of manual testing?” tab_id=”1584633487494-67ee5725-7302″][vc_column_text]De-merits of manual testing are:

  • Highly susceptible to human error and are risky
  • Test types like load testing and performance testing are not possible manually
  • Regression tests are really time-consuming if they are done manually
  • Scope of manual testing is very limited when compared to automation testing
  • Not suitable in very large organizations and time-bounded projects
  • The cost adds up, so, it’s more expensive to test manually in the long run

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What’s the role of documentation in Manual Testing?” tab_id=”1584633488647-ca1e57bf-c222″][vc_column_text]Documentation plays a critical role in achieving effective software testing. Details like requirement specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. should all be documented.

Documenting the test cases will facilitate you to estimate the testing effort you will need along with test coverage and tracking and tracing requirement. Some commonly applied documentation artifacts associated with software testing are:

  1. Test Plan
  2. Test Scenario
  3. Test Case
  4. Traceability Matrix

With this, we have completed basic question based on manual testing. In the next part of this Manual Testing Interview Questions article, let’s discuss advanced level questions related to manual testing.[/vc_column_text][/vc_tta_section][vc_tta_section title=”What is the difference between manual testing and automation testing?” tab_id=”1584633489564-46f1e004-248c”][vc_column_text]

Manual Testing Automation Testing
In manual testing, the accuracy, and reliability of test cases are low, as manual tests are more prone to human error. Automated testing, on the other hand, is more reliable as tools and scripts are used to perform tests.
The time required for manual testing is high as human resources perform all the tasks. The time required is comparatively low as software tool execute the tests
In manual testing investment cost is low, but Return of Investment(ROI) is low as well. In automation testing investment cost and Return of Investment, both are high.
Manual testing is preferred when the test cases are run once or twice. Also suitable for Exploratory, Usability and Adhoc Testing.  You can use test automation for Regression Testing, Performance Testing, Load Testing or highly repeatable functional test cases
Allows for human observation to find out any glitches. Therefore manual testing helps in improving the customer experience. As there is no human observation involved, there is no guarantee of positive customer experience.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”What are the phases involved in Software Testing Life Cycle?” tab_id=”1584633490695-97ff9f60-7d30″][vc_column_text]The different phases involved in the software testing life cycle are:

Phases Explanation
Requirement Analysis QA team understands the requirement in terms of what we will testing & figure out the testable requirements.
Test Planning In this phase, the test strategy is defined. Objective & the scope of the project is determined.
Test Case Development Here, detailed test cases are defined and developed. The testing team also prepares the test data for testing.
Test Environment Setup It is a setup of software and hardware for the testing teams to execute test cases.
Test Execution It is the process of executing the code and comparing the expected and actual results.
Test Cycle Closure It involves calling out the testing team member meeting & evaluating cycle completion criteria based on test coverage, quality, cost, time, critical business objectives, and software.

[/vc_column_text][/vc_tta_section][vc_tta_section title=”When should you opt for manual testing over automation testing?” tab_id=”1584633491772-3409b635-b340″][vc_column_text]There are a lot of cases when manual testing is best suited over automation testing, like:

  • Short-time projects: Automated tests are aimed at saving time and resources yet it takes time and resources to design and maintain them. For example, if you are building a small promotional website, it can be much more efficient to rely on manual testing.
  • Ad-hoc Testing: In ad-hoc testing, there is no specific approach. Ad-hoc testing is a totally unplanned method of testing where the understanding and insight of the tester is the only important factor. This can be achieved using manual testing.
  • Exploratory Test: This type of testing requires the tester’s knowledge, experience, analytical, logical skills, creativity, and intuition. So human involvement is important in exploratory testing.
  • Usability Testing: When performing usability testing, the tester needs to measure how user-friendly, efficient, or convenient the software or product is for the end-users. Human observation is the most important factor, so manual testing sounds seems more appropriate.

[/vc_column_text][/vc_tta_section][/vc_tta_accordion][/vc_column][/vc_row]

WhatsApp us