Problem
The client was serving thousands of users through a platform that was not timely tested.
Bug-free breakthrough
A software testing success story
Michael Way
client’s feedback
Ensure
quality
quality
Flawless
user experience
user experience
Project Brief
Solution
Testing the platform simultaneously while developers and customers interacted with the same.
About the Client
Founded in Bournemouth in 2009, Transpond (earlier known as MPZEmail) is a brainchild of an experienced developer- Mike Way. He holds more than 28 years of experience in the field of development and understands the importance of testing.
Transpond is an easy-to-use marketing platform that gives you all the tools you need to communicate with your contacts and also future-proofs the way you do it. The platform was serving thousands of customers on a daily basis and growing at a fast pace.
With the platform growing rapidly, Mike understood that the process of testing could not be ignored any further. He wanted to ensure a bug-free experience for old and new clients.
Concerns of Transpond
The client had a pre-existing platform that was used by thousands of users to manage email marketing campaigns. But the platform was clouded with bugs at every step.
Issues at Hand
No In-house Testing
20-25% of the users abandoned the platform,
if they faced a recurring issue.
Deteriorating User Experience
New or recurring issues on the platform were not getting fixed before new updates were released.
Conducted a Dry Run
Our team conducted initial tests and prepared a report that discussed various reasons for bugs cropping up at every step. We used Selenium to conduct tests.
Unstable Test
Environment
Environment
Compatibility
Issues
Issues
Poor Integration
of Test Results
of Test Results
Monitoring
& Alerting
& Alerting
Results
Captured
The errors associated with the functionality of a specific software component are called functional bugs.
Examples: A button doesn't submit the form, the search doesn't react to the user input, the app crashes.
At the initial stage, we understood that most of the bugs could be listed under functionality issues.
Laid Down
the Test Bed
Shared a Test Plan
To keep the client on the same page and ensure everything is as per the expectations, we drafted a test plan. A test plan is a detailed document that describes software testing areas and activities.
It is the most crucial activity which ensures the availability of all the lists of planned activities in an appropriate sequence.
Check out the test plan
Wrote Test Scripts
A test script is a short program written in a programming language. It is used to test a part of the functionality of a software system.
- Helped us outline what should be done to check the software.
- Provided a clear picture of the expectations that need to be achieved.
- Helped us show how we addressed and tested all the requirements.
Reported the Issues
To help Michael track all the bugs (coding errors in a computer program found using the testing phase) and the progress of the project, we compiled a detailed report that contained severity/priority, visual proofs, the status of the bugs, and much more.
Attained
Results
Through regression testing using Selenium, we were able to minimize functional bugs and improve the user experience on the platform.
Regression Testing is responsible for the overall stability and functionality of the existing features.
It ensured that the platform functioned as expected after any code changes, updates, or improvements.
100+
Time Spent on Debugging
10%
MoM Increase in User engagement
200+
Bugs Rectified
200k
Monthly Users
Surpassing
Daily Expectations
Proficiency in: Functional & Non-Functional Testing, System Testing, Load Testing, Reliability Testing, Feature Testing, Mobile App Testing, and Validation.
The project required knowledge of operating systems such as Linux, Windows, iOS, and Android. Vikash not only took care of the daily tasks but also played a key role in improving the platform through his inputs and industry know-how.
Headups for
Automation
As the project progressed swiftly under the guidance of Vikash, Michael gave a thumbs-up for automated testing. This helped the analyst team to perform tests at a faster pace and skip repeated tests.
Manual Testing
- Performed by quality assurance and testing team
- Suitable for exploratory, usability, and ad hoc testing
- Should be performed when experienced and talented quality assurance and testing experts are available
- Is less reliable as it is prone to human errors
Automation Testing
- Performed using software testing tools
- Suitable for white box testing, load testing, and performance testing
- Any test that needs to be repeated occasionally during the development process should be automated
- Is fast and reliable as it runs using tools and per-written test scripts
JMeter was used to simulate a heavy load on a server, group of servers, network, or object to test its strength or to analyze overall performance under different load types.
- Provided options for tweaking uncommon scenarios
- Offered log debugging and sampling
