Please enable JavaScript.
Coggle requires JavaScript to display documents.
Types Of Testing (Alpha Testing (Advantages (Clear view of the reliability…
Types Of Testing
Alpha Testing
Description
It is the most common type of testing used in the Software industry. The objective of this testing is to identify all possible issues or defects before releasing it into the market or to the user. Alpha testing is carried out at the end of the software development phase but before the Beta Testing.
-
-
Acceptance Testing
Description
An acceptance test is performed by the client and verifies whether the end to end the flow of the system is as per the business requirements or not and if it is as per the needs of the end user.
-
Disadvantages
-
End users may focus on comparing the new system to a legacy system, rather than looking for defects.
Ad-hoc Testing
Description
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.
Advantages
Software Developer is free to apply his/her own ways of testing, which helps find more defects within the codebase.
Adhoc testing can be done any time in the SDLC, without needing to follow any formal processes
-
Documentation is not necessary when software tester is doing this type of testing instead of that tester must have to focus more on the testing of the feature/application without worrying about the formal documentation.
Disadvantages
Since ad-hoc testing is done without any planning and in unstructured way so recreation of bugs sometime becomes a big trouble.
The test scenarios executed during the ad-hoc testing are not documented so the tester has to keep all the scenarios in their mind which he/she might not be able to recollect in future.
Ad-hoc testing is very much dependent on the skilled tester who has thorough knowledge of the product it cannot be done by any new joiner of the team.
Accessibility Testing
Description
The aim of accessibility testing is to determine whether the software or application is accessible for disabled people or not. Here disability means deaf, color blind, 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.
Advantages
Many people have disability issues that affect their use of software. To avoid isolating users, an application needs to be made accessibility friendly. Accessibility legislation exists in many countries. If an application does not comply, there is a risk of financial penalties and/or legal action.
Disadvantages
Software testing is a complex process whether it’s automated, manual or a combination of both. Although there are many automation tools available, they do not necessarily help in every situation. It is a difficult area to replace human intuition and reasoning that manual human checks provide.
Accessibility testing is still in its infancy which causes inconsistency. In the future, there will be a more standard and consistent way to test your application’s accessibility.
Beta Testing
Description
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.
Advantages
You have the opportunity to get your application into the hands of users prior to releasing it to the general public.
Users can install, test your application, and send feedback to you during this beta testing period.
Your beta testers can discover issues with your application that you may have not noticed, such as confusing application flow, and even crashes.
Disadvantages
Doesn’t allow any control over the testing as it is carried out in real environment and not under the lab environment.
-
Back-end Testing
Description
In back-end testing GUI is not involved, 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
Advantages
Backend testing is way ahead of black-box testing and testing is actually focused at data and its organisation level into the database.
-
-
Disadvantages
Manual tester requires SQL knowledge in order to interact with database components such as views, tables, triggers, stored procedures, functions, etc.
-
-
Black Box Testing
Description
Internal system design is not considered in this type of testing. Tests are based on the requirements and functionality.
Advantages
-
-
Tester is free from any pressure of knowledge of specific programming languages to test the reliability and functionality of an application / software
-
-
Disadvantages
Testing every possible input stream is not possible because it is time-consuming and this would eventually leave many program paths untested
-
-
-
-
Component Testing
Description
It is mostly performed by developers after the completion of unit testing. Component Testing involves testing of multiple functionalities as a single code and its objective is to identify if any defect exists after connecting those multiple functionalities with each other.
-
-
White Box Testing
Description
White Box testing is based on the knowledge about the internal logic of an application’s code. It is also known as Glass box Testing. Internal software and code working should be known for performing this type of testing. Under this tests are based on the coverage of code statements, branches, paths, conditions etc.
Advantages
-
Tester can ask about implementation of each section, so it might be possible to remove unused lines of code which might be causing introduction of bug.
To start the testing of the software no need to wait for the GUI, you can start the White Box Testing.
As the tester is aware of internal coding structure, then it is helpful to derive which type of input data is needed to testing software application effectively.
-
-
-