Exploratory Testing on ScrapeAnyWeb.site(SAW)

Olamide Ogunyemi — Wed, 03 Jul 2024 14:23:48 +0000

In today's blog post, I'll be walking you through the SAW application I tested using the Exploratory testing technique. Exploratory testing is a technique which provides an element of freedom to manually test a site in a sensible fashion by investigating and discovering the functionality without pre-defined scripts or test cases. Exploratory testing can take place as soon as software is available, but a tester's involvement should begin much earlier. Without carrying out exploratory testing, there’s an increased risk of missing not only significant functional issues but also the small details that users will notice. When you follow a script or a strictly defined set of test cases, you'll be focusing so much on making sure the software matches what’s written down that you miss things around you. Whereas, When you explore software, you’re looking for anything that seems out of place such as testing values and inputs that people may not have considered.

During my exploratory test experience on the SAW website. I carefully navigated through the functionality, user experience, compatibility, and performance to identify where the software is broken, and how it can be improved.

While at the exercise, I identified several key issues which includes the following:

Absence of pointer cursor change: Buttons do not show a cursor change to indicate they are clickable.
Slow page load times: there were noticeable delays of about 2-3 seconds before the intended actions are executed when buttons are clicked. An instance of occurrence was for "change" button and "add URL" button.
Application unexpected closure: The application unexpectedly closes, causing interruption.
Statistic mismatch: the scrape statistic did not match the derived data.
Inadequate error message: an error message was not received when the "Start Scraping" button was clicked upon without providing a URL link. You can find the full bug report here.

In lieu of the issues highlighted above, I'll suggest the following suggestions;

Absence of pointer cursor change: Update the code to ensure all buttons change the cursor to a pointer when hovered over.
Slow page load times: Review and optimize the code executed when the "Change" or "add URL" button is clicked to ensure efficiency.
Application unexpected closure: Conduct extensive stability and stress testing to identify and fix crash-inducing issues. Also, allow for recovery after unexpected closures.
Statistic mismatch: Implement validation checks to ensure that the number of derived data entries matches the reported scrape counts.
Inadequate error message: Display clear error messages when required fields are left blank, guiding the user to correct the issue. For a detailed overview, please refer to the full bug report here.

In conclusion, When you explore software, you’re looking for anything that seems different. Testers are always on the lookout for inconsistencies, values and inputs that people may not have considered. Having explored testing the SAW website, it is expedient that the developers would make a better decision when the suggestions are implemented. And in turn, make a better software for users.

An Exploratory Testing Approach on HNG.TECH

Olamide Ogunyemi — Sat, 29 Jun 2024 18:19:46 +0000

Exploratory testing is an approach to software testing that is often described as simultaneous learning, test design, and execution. It focuses on discovery and relies on the guidance of the individual tester to uncover defects that are not easily covered in the scope of other tests. The practice of exploratory testing has gathered momentum in recent years. Testers and QA managers are encouraged to include exploratory testing as part of a comprehensive test coverage strategy.

This weekend, I conducted an exploratory test on hng.tech website. My goal for the testing was to uncover issues that could affect user experience and its overall functionality.

During the exploratory test, I identified several key issues which includes the following:

Deadlinks: some links were unresponsive.
Broken Links: leading to error 404 error page.
Slow Page Load Times: for example, "contact us" link took a long time to load.
UI/UX Inconsistencies: some elements were not consistent. An example was the course design.
Typo error: Some texts had existing typo error.
Blank Text Fields: some displayed texts fields were blanks
Inactive buttons: some navigation buttons were non-functional. These were some of the highlighted issues amongst others. You can find the full bug report here.

However, I'll suggest the following as a medium of improvements to a better functioning and user friendly website;

Deadlinks: Regularly audit and update links to ensure they point to the correct destinations.
Broken Links: Monitor server logs to detect and fix broken links promptly.
UI/UX Inconsistencies: Regularly review the design to maintain uniformity.
Typo error: Implement a rigorous proofreading process before publishing content.
Blank Text Fields: Ensure all text fields are correctly populated with data.
Inactive buttons: Test all buttons and fix any backend issues causing buttons to be inactive. By implementing these suggested improvements, the website can provide a seamless and engaging experience for all users. For a detailed overview of all identified issues, please refer to the full bug report here.

Conclusively, exploratory testing on the hng.tech website unveiled several areas needing improvement to enhance user satisfaction and gaining insights into the overall functionality and user experience of the website. I highlighted above, several areas for improvement that, when looked into, can significantly enhance functionality of the website. Above all, the results of exploratory testing provided a user-oriented perspective and feedback to the development teams. The goal which was to find million-dollar defects that are generally hidden behind the defined workflow was successfully accomplished.

DEV Community: Olamide Ogunyemi

Exploratory Testing on ScrapeAnyWeb.site(SAW)

An Exploratory Testing Approach on HNG.TECH