Automated Test

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 5

Title: Software Manual Testing Vs.

Automated Testing
Objective: Students will be able to differentiate between Manual testing and automated Testing.
Summary of Task/Action:
1. The class will start with an activity to introduce the students to manual testing.
a. If each student has a laptop, the activity will be individual. Else, the activity will
group by 5.
b. Students must execute a manual testing given the test cases and website.
c. Time allotted for the activity will be 3 mins.
2. Lecture about:
a. What is Manual Testing?
3. The instructor will demo a sample automated testing tool to execute the test cases given
on the first activity.
4. Lecture about:
a. What is Automated Testing?
b. What is the difference between manual and automated testing?
c. Why use Automated testing over Manual testing?
d. Why use Manual testing over Automated testing?
5. As a conclusion, the instructor will ask a representative of each group to compare the
results of manual testing and automated testing. If the first activity was done individually,
the instructor will pick a few students to compare the result.
References:

https://www.perfecto.io/blog/automated-testing-vs-manual-testing-vs-continuous-testing
August 13, 2019
Eran Kinsbruner

Source: Manual vs. Automated Testing: The Eternal Debate is Over - QA Madness Software testing
company
Kate Punova
https://www.qamadness.com/manual-testing-vs-automated-testing/

https://www.testim.io/blog/test-automation-vs-manual-testing/
Test Automation vs Manual Testing: Picking the Right Balance
By Testim, October 29, 2019 Michiel Mulders

https://www.scnsoft.com/blog/manual-vs-automated-testing
Alexander Viktorov
Manual Testing Vs. Automated Testing Vs. Integrated Approach: The Right Way to Test Modern
Apps
When you are in IT industry, might be a graphic designer, animation or in
programming/software developers or in any other track ensuring the quality of
the product you produce is crucial.
Software testing is an integral part of the development of a successful
software project. Software testing itself consists of a huge domain in which
many variants exist. To give you an idea, some examples of test
methodologies are regression testing, smoke testing, network testing,
integration testing, and many more.

With this abundance of testing formats, comparison between manual and


automated testing becomes actively discussed.
In relation with that, today I will discuss Software Manual Testing vs.
Automated Testing.

To have a better understanding of the topic, we will first have an activity. If


each student has a computer this activity will be done individually, but if it
lacks a computer we will have a group consisting of 5 members.

When You are doing a software testing you must have documentation or flow
on how you will execute your testing. Especially when you are doing it
manual, a test plan is necessary.

For now I have provided a test plan which you will follow, I have given a
website that you have to access and you have to execute the test cases on
the test plan manually. Follow the format.

● Is there a group who finished the testing?


● What do you think are the reasons why you were not able to finish
testing?

What is Manual Testing?


● Manual testing is the process in which testers execute tests one-by-one in an
individual manner.
● The purpose of manual testing is to catch bugs and feature issues before a software
application goes live.
● Manual testing is very hands-on. It requires Qa testers to be highly involved in
everything from test case creation to actual test execution.

Let me show you an example of testing using automation. In this example I used katalon studio
as my test tool,
Here I have created test steps by using record and play features, or by creating test scripts.
(insert katalon studio.)

What is Automated Testing?


Automation testing is the process in which testers utilize tools and scripts to automate testing
efforts.
Automation testing helps testers execute more test cases and improve test coverage. When
comparing manual vs. automation testing, manual takes longer. Automated testing is more
efficient.
Automation testing involves testers writing test scripts that automate test execution. (A test
script is a set of instructions to be performed on target platforms to validate a feature or
expected outcome.)

What is the difference between manual and automated testing?

In manual testing, a testing engineer (a human) manually executes test cases. This means the
testing engineer describes several scenarios and edge cases that they want to verify the
functioning of. Manual testing doesn’t use any tools or scripts. This means that the testing
engineer has to prepare a dataset and the scenario and trigger the right inputs or actions to test
the described scenario.

With automated testing, all of this—as the name suggests—is automated. This means using
scripts and tools that prepare data and a state, then execute the steps required to verify the
scenario in an automated way.

Both manual and automated testing have benefits and disadvantages. It’s worth knowing the
difference, and when to use one or the other for best results.

Why use Automated testing over Manual testing?

Major benefits of automated testing:


● Speed: Although they may take longer to launch, automated test execution is faster than
manual operations. For increased speed, automated tests can be parallelized and run
simultaneously on several browsers, platforms and devices.
● Re-usability: Once created, test code can be used as many times as required.
● Immediate results: Test results are generated automatically and become available in real
time for all testing stakeholders.
Apart from that, automated tests offer the following advantages:
● Automated tests can run unattended (e.g., to verify nightly builds when testing goes in
parallel with development).
● Automated tests are not prone to human error.
● Automated testing offers reduced costs in the long run.

At the same time, automated testing has its own weaknesses:


● Requirement changes will entail test code adjustments for all relevant test cases.
● Some tests are too complicated to automate.
● Automated tests check only the pre-defined problems.
● Automated tests take time to develop.
● Automated testing requires programming skills and domain knowledge.
● Testing tools, test code verification and maintenance entail additional costs.
● Tools for automated testing can have their own bugs.

Why use Manual testing over Automated testing?


Manual testers simulate all steps of a user journey and check that users see exactly what they
need to see and that an application sends and processes requests as it is supposed to.

Major benefits of manual testing:


● User perspective: Only a pair of human eyes can spot such issues as inconvenient
workflows and design, fonts, sizes, and unclear error messages, etc.
● Flexibility: Manual testers have the freedom to employ creativity and question things that
were not prescripted.
● Adaptability: Manual testers can verify new features or any changes in design without
special preparation.

Additionally, the manual testing process provides the following opportunities:


● It can handle user journeys of any complexity.
● It is relatively quick to launch.
● It is low-cost in the short run.

However, testing by hand has the following weaknesses:


● Some testing types can hardly be accomplished manually (stress, load, scalability
testing).
● Manual tests are subject to human errors and inconsistency.
● Repeated tasks (like regression testing) are tedious for testers and expensive for large
projects.

Manual testing is suited for usability testing, ad-hoc testing, and exploratory testing.
Usability testing focuses on measuring an application’s user-friendliness. Ad-hoc testing uses a
free approach in which the testing engineer tries to break components without a set scenario.

The last approach, exploratory testing, focuses on the tester’s knowledge, experience, analytical
skills, creativity, and intuition. Here, the test is characterized by poorly written specification
documentation or a short time for execution.

-----
Automation testing will not replace manual testing. You need both manual and automation
testing. Manual testing handles complex test cases, while automated testing handles simpler,
more repetitive tests.

So, manual testing is still important. But adding automated testing makes your manual tests
more efficient.

Notably, automated and manual testing can’t exist separately. The team of automated QA
engineers completes a test checklist following manual test cases. When QA specialists adopt
multiple benefits and take into account drawbacks of these approaches, they conduct a
complex, professional software quality assurance. Robust automation brings about efficiency in
the whole testing process, while manual testing remains less costly and more helpful checking
user interface.

There is no universal way of testing; each project requires a unique approach. Thanks to the
combination of manual and automated testing, it’s possible to detect all the possible software failures
at early stages. If you are to implement a combined QA strategy in your project, think of its budget,
deadline, and team`s skillset. Looking for a QA team to test your software, choose the one that
offers a combined strategy. In such a way, you will reap the advantages of both methods.

You might also like