Application Testing and Deployment Flashcards
refers to the process of testing any
software application using scripts, tools, or any test automation frameworks in order to identify errors.
Application Testing
Two ways to perform application testing:
Manual Testing
Automated Testing
testing approach used more frequently by developers in the initial phases of the development for testing specific features
Manual Testing
Once the software application is entirely
developed, QAs automate test scenarios or test cases from the end-users’ perspective to evaluate the usability, functionality,
and performance of the application.
Automated Testing
are used to verify that the application functions as expected under specific conditions.
Test cases
are used to verify that an application works
as expected overall. A test scenario consists of multiple test cases with detailed instructions about how to test specific
end-to-end functionality and user experience
Test scenarios
refers to a test process
in which a QA manually tests the software application in order to
identify bugs.
Manual Testing
Stages of Manual Testing
Unit Testing
Integration Testing
System Testing
Acceptance Testing
Types of Manual Testing
White Box Testing
Black Box Testing
Grey Box Testing
involves verification of individual components or units of
source code.
It focuses on testing the functionality of individual components
within the application.
Unit Testing
the next step after unit testing.
Multiple units are integrated to be tested as a whole. For example, testing a series of application interfaces in a particular
order to verify interoperability.
Integration Testing
Involves testing all the integrated modules of the application as a whole.
It helps QAs verify whether the system meets the desired requirements
Teams perform several types of system testing like regression testing, stress testing, functional testing and more, depending on their access to time and resources
System Testing
The main goal of this stage is to verify whether the system as a whole is fit for use in the real world.
Performed both internally and externally.
Internal acceptance testing (also known as alpha testing) is performed by
the members within the organization.
It also identifies bugs in the last stage before releasing a
product.
Acceptance Testing
Also known as the beta testing is performed by a limited number of actual end-users. This approach helps teams evaluate how well the product satisfies the user’s standards.
External testing
Also known as glass box or transparent testing, is an approach in which the QA is familiar with the internal code or structure of the application. It is primarily used for unit testing.
White box Testing
a test approach in which the QA
doesn’t have any knowledge about the underlying code or structure of the application.
Black-box testing
The combination of both white box and black box testing techniques. The main aim of this approach is to identify any bugs present either due to inappropriate usage or any structural flaws.
Grey-Box testing
What tests should be automated?
Regression Testing
Testing of complex functionalities
Smoke Testing
Getting Started with Automation Testing
Do not aim for 100% test automation.
Set a realistic goal
Explore
Is an integral part of any testing ecosystem. Without moving to an automation setup, comprehensive testing becomes difficult, as do the meeting of ever-shortening
deadlines.
Automation testing
Is the most popular tool suite for automating web application testing.
Selenium
