Manual Testing

The following categories of validation approaches are included in functional testing:

• unit testing
• smoking testing
• UAT sanity testing
• interface testing
• integration testing
• system testing
• regressive testing

White box testing examines the internal data structures, internal design, code structure, and operation of the software. It is also known as structural testing, transparent box testing, and glass box testing. Statement coverage, branch coverage, and path coverage are its techniques.

Functional testing involves evaluating the "functionality" of the program or application that is being evaluated. It examines how the software under test behaves. Finding out how many users would sign into a programme at once is a nice example of a non-functional test.

Important Distinctions Between Functional and Non-Functional Testing

• Non-functional factors like performance, usability, reliability, etc. are verified by non-functional testing, each function or feature of the software is verified by functional testing.
• Non-functional testing is challenging to carry out manually, functional testing can be done so.
• Non-functional testing is based on client expectations, functional testing is based on customer requirements.
• Non-functional testing seeks to evaluate the performance of the software, functional testing aims to validate software actions.
• The login functionality is an example of functional testing, whereas the dashboard should load in two seconds is an example of non-functional testing.

A structured and organized approach to test execution is suggested by the software testing life cycle (STLC). Such as analysis of requirements, planning a test, case development for tests, execution of the test environment setup, and closure of the test cycle, etc.

Regression testing has a subcategory known as sanity testing. Sanity testing is carried out after getting the software build to make sure the introduced code changes are operating as anticipated.

An error is defined as a code blunder. A defect is created when a manual tester finds an error. A bug is a flaw that the development team acknowledges. A created piece of code fails functionally if it falls short of the criteria.  

A bug is a discrepancy between the expected result and the actual result in an application or a module that is discovered by the testing team throughout the testing period.
 
Defects are discovered when an application's functionality does not meet customer expectations. Giving incorrect input could result in a flaw, as could any coding fault.
 
An error might happen as a result of a developer's coding mistakes due to misinterpretation of the requirement or the demand was not expressed correctly. This is known as the problem in code that leads to errors.

Expect to come across this popular question in manual testing interview questions.

• Unit/component testing: Unit testing seeks to confirm that each one is correct in terms of meeting the requirements and having the required functionality.
• Integration testing: Integration testing tries to evaluate various system components in combination to determine whether they function properly together.
• System testing: System testing gives testers a chance to check that the product complies with business requirements and that its working environment doesn't present any problems
• Acceptance testing: Acceptance testing is done to ascertain whether the system is prepared for release.

The term "severity" refers to a bug's weight or depth.  It indicates which bug should be fixed first in terms of priority. It describes the viewpoint of the user.

A bug's criticality can range from low to high, depending on the situation.

• Low user interface flaws
• Medium: level faults at boundaries
• High calculation errors
• High Data misinterpretation
• High Hardware malfunctions

User interface testing, sometimes referred to as UI testing or GUI testing, examines the visual components of the application to confirm that they function as intended and perform as anticipated.

The higher-level modules in this top-down method are evaluated first, followed by the lower-level modules. The modules are then appropriately integrated. Lower-level modules here relate to submodules, while higher-level modules refer to the main module. This method makes use of Stubs, which are mostly used to emulate the invoked submodule; if it is not developed, the Stub serves as a temporary replacement.
 
The lower-level modules in this Bottom Up technique are tested first, followed by the higher-level modules. The modules are then appropriately integrated. Higher-level modules here relate to core modules, whereas lower-level modules refer to submodules. This method makes use of test drivers, which are primarily employed to initiate and pass necessary data from upper-level modules to lower-level modules as necessary.

The percentage of testing that has been done for a product is indicated by the quality indicator known as test coverage. Both functional and non-functional testing operations can benefit from it. To fill in for missing test cases, this metric is employed.

Defect Removal Efficiency is the capacity to eliminate flaws that a project introduces into a system throughout the project life cycle. DRE = (total flaws discovered during the project/total defects introduced by the project) x 100.

Regression testing is software testing that is used to confirm that any update or modification to software doesn't alter the software's general functionality.

A defect cycle, referred to as a bug life cycle, occurs throughout the defect's existence. As it is governed by the software testing process and also dependent on the tools employed, it differs from organisation to organisation and also from project to project.

• Clear and univocal.
• Title, and description
• Briefly presented information
  
  

When a client or end-user finds a bug the testing team can find it. Another term for this is bug leakage, which occurs when a bug is found that was present in a previous build.

When a build is given to the testing team knowing that it contains a flaw, this is referred to as a bug release. The priority and severity of the bug are low. When the consumer requests the application on time, it is completed. The customer is willing to put up with a bug in the program that has already been released as well as the time and money it will take to fix it. The Release Notes given to the client list these problems for potential future improvement.

Exploratory testing is a method of software testing in which testers gain knowledge of both the test design and test execution at the same time. To put it another way, it's a hands-on method where testers are more involved in the test execution than in preparation.

It is a bug that is a severe roadblock and has interfered with the functionality of the entire website or application.

A defect that was either hidden or concealed and was not apparent upon reasonable or customary examination or inspection. All about latent defect:

• The time limit for lateral defects can be extended up to six years from the date the cause of action was first identified.
• It's a unique software flaw that is an error that hasn't happened yet. It is mostly a systematic fault that appears in software while it is being produced and even gets beyond the early testing, which includes pre-production and extended use.
• One type of fault that persists after a product is produced is a latent one.
• Modern software testing methods and cutting-edge technology have been developed to eliminate flaws, however unanticipated flaws still exist.
• In order to identify the flaws, software testers should use and comprehend the proper test cases.

Acceptance testing is a quality assurance (QA) procedure that makes sure how well an application obeys the needs of end users.

Key features of acceptance testing

• Users are actively involved in the testing process, which allows the project team to understand the users' additional requirements.
• Executing tests automatically.
• Due to involvement in the testing process, clients feel confident and satisfied.
• The user can describe their needs more easily.
• It just covers the Black-Box testing procedure, therefore the complete product's functionality will be examined.

A common question in manual testing interview questions for experienced, don't miss this one. 

A procedure called "defect triage" is used to rank defects according to their seriousness, risk, and frequency of occurrence. Though triaging can be used on projects of any size, its advantages are more pronounced and palpable in larger projects.

A stub is a little piece of code used in testing to replace another component. Using a stub has the advantage of returning consistent results, which makes the test easier to construct. And tests can be performed even if the other components are not yet operational.

A tool for testing that automatically compares actual findings to projected results. 

Features of test comparators :

• Quickly compare transitory events that occur during test execution
• Post-execution comparison of stored data, such as that found in files or databases
• Mask or filter the subsets of actual and expected outcomes.

A requirement stack might not be offered for a particular product. If a program contains significant unanticipated functionality, it may take some work to identify it; this would point to more fundamental issues with the software development process.

Before deciding which testing to choose consider such as Periodic execution, recursive repetitive steps are easily tested, tests run in a typical runtime setting, automation speeds up the process, and reusability.

Boundary value analysis is used to locate faults near the edges of the input domain. Boundary value analysis and equivalence partitioning have a relationship and can be applied in tandem at all testing levels.