Home
Case Studies
QA for AI powered Media Marketplace

Jul 04, 2023 3 min read

QA for AI powered Media Marketplace

Marketing

Marketplace

Platforms:

Web

Country:

Singapore

Implementation time:

Aug 2021 – Present

about company

Vidiverse is one of the leading worldwide Microstock marketplaces for video makers internationally. The vibrant marketplace offers everything from stock videos, music, 3D models, After Effects, and Apple Motion templates bundled with transparent, royalty-free licensing.

For this project, Luxe Quality provided skilled Backend QA, Manual QA, and Automation QA / Team Lead. We strived to achieve maximum test coverage through automated testing, which was crucial in verifying the software system's functionality, performance, and reliability. By aiming for complete test coverage, we ensured that all critical scenarios and edge cases were thoroughly tested, reducing the risk of potential issues or regressions.

before

When we started working on this project, there were nearly 100 E2E tests, which took 1 hour to execute, and 200 Postman + Newman smoke tests for implementing API tests. There was no documentation on the project, and the test coverage was unknown.
Our task was to update the backend and frontend test frameworks for the client's project.

challenges and solutions

Challenges	Solutions
Unknown coverage: probably less than 10%	Developed 2000 E2E automation tests with Allure reports, achieving almost 90% functionality test coverage
Execution time: nearly 100 E2E tests took 1 hour to execute	Optimized tests and created standard methods, reducing the test execution time to approximately 30 minutes. Even though the number of cases has increased significantly
Diverse testing requirements: needed to test front and backend	Utilized specific tools and methodologies, such as Postman and Runscope (BlazeMeter), to conduct API and contract testing for the backend. Developed test plans and checklists for frontend testing. Employed a combination of manual and automated testing to cover all testing requirements. Manual Testing: Functional, Usability, Accessibility, Regression, Security, E2E. AutomationTesting: Functional,
No documentation	Created specific level test plans, checklists, and more than 1000 bug reports to document the testing process. Also, set up reporting after tests
Unclear test results without a reporting system	Implemented a reporting system to generate clear and concise test reports. Test results were documented and shared with the project manager to inform them of progress and enable better decision-making
Ensuring continuous improvement and adherence to standards	Introduced testing standards and best practices, such as Code freeze for release stability and standardized bug reporting. Conducted regular assessments and evaluations of the testing process to identify areas for improvement. Implemented state monitoring and focused on continuous learning and development within the QA team

technologies, tools, approaches

The project utilized various technologies, including Webdriver.io, Postman, Burp Suite, Runscope, GitHub Actions, Allure Reporter, OpenAPI, CIrcleCI, AWS S3, GTM, Qase, and Jira. We also established Code Freeze for Release Stability, Standards for Bug Reports, and Testing Standards and focused on continuous improvement.

The implementation of these practices has had a positive impact on various aspects of application quality and user experience. Code freezes have provided a stable foundation for releases, reducing the risk of introducing new issues and ensuring excellent stability.

features of the project

The involvement of QA Engineers in requirements and development was a critical aspect of the project. Another significant aspect was the complete migration to a new backend and frontend framework. For this project, we also implemented TestOps.

results

Migration to the latest technologies went smoothly and seamlessly. Users reported minimal issues on production. Any arising problems were mainly related to some extra or individual cases. The customer's requirements were effectively fulfilled, and the project received ongoing support.
We had 2200 TMS test cases throughout our active collaboration covering all application roles. These cases were accompanied by 2000 E2E tests with an Allure report, deployed on the server, and saved in history. Test execution now takes nearly 30 min. We also have 1700 E2E API tests with contract testing.
Code freezes provide a stable foundation for releases, minimizing the risk of introducing new issues. Implementing standardized bug reports improved communication between testers and developers, leading to faster bug resolution.

Adherence to testing standards facilitated a comprehensive and consistent approach to testing, ultimately enhancing the overall software quality. We implemented the best practices of QA to this project for testing and decreasing development risks. The application was successfully released.

Implementation Steps

1. User Stories Testing

In the initial phase, the testing process began with the current testing process's audit and analysis, gathering stakeholders' requirements and examining user stories to gain a deeper understanding of the product and its purpose. These steps hold great significance in testing as they allow testers to grasp the user's mindset and consider various possible interaction scenarios with the product, even those that may seem less likely.

2. Communication with Developers and Preparing Test Data

Our QA engineers closely collaborated with developers to understand the technical aspects of the software, clarify requirements, and discuss any potential challenges or limitations. They also worked to identify and prepare the necessary test data, ensuring that the test environment accurately simulated real-world scenarios and covered various use cases.

3. Develop a Proof of Concept (POC) and Present it to the Client and Stakeholders

Developing a proof of concept involves creating a small-scale version of the automated testing framework or a specific test scenario to demonstrate its feasibility, functionality, and benefits. The POC showcased the potential of automation in terms of time and effort savings, improved test coverage, and enhanced reliability. Subsequently, the POC was presented to the client and stakeholders for support, approval, and investment in further automation efforts.

4. Migrate to a New Testing Framework

The migration process involved transitioning the existing tests, frameworks, and test data to the new environment. QA engineers ensured that the migration was smooth and seamless by conducting thorough testing to validate the functionality and compatibility of the system in the new framework. They also addressed any issues or discrepancies during the migration process.

5. Writing the First 300 Tests for the Highest-Priority Functionality

To ensure comprehensive test coverage, QA engineers prioritize the highest-priority functionalities directly impacting the software's core functionality and user experience. They design and write the initial 300 tests to cover critical scenarios, including payment processing and account loading. These tests help validate these crucial features' reliability, accuracy, and performance, ensuring they meet the required standards and specifications.

6. Generate a Report on the Coverage Achieved by Manual and Automated Tests

QA teams assessed the effectiveness of their testing efforts by generating a report that analyzed the coverage achieved through manual and automated testing. This report provided insights into the number of tests executed and the percentage of coverage for various functionalities and identified any gaps or areas that required further attention. It served as a valuable resource for evaluating the overall quality of the software and guiding future testing efforts and improvements.

7. Performing Various Types of Testing with the Functionality That Was Developed

Functional Testing
Non-Functional Testing, such as Security, Usability, and Accessibility Testing
Black-Box Testing and White-Box Testing,
Acceptance and Regression Testing
End-to-End (E2E) Testing,
API Testing,
Automation Testing

SEO Checks: Evaluating the application's adherence to search engine optimization best practices to improve its visibility and ranking in search engine results.

Our team helped ensure the system functions correctly, met requirements, performed well, and provided a secure and user-friendly experience. Once the setup was completed, we conducted re-tests and regression testing every sprint (2 weeks). Additionally, we provided testing reports to the project manager to keep them informed of our progress.

client's feedback

To read the client's review for this project, click here.

Services provided

Manual testing
Regression testing
Functional testing
Automation testing
Usability testing
Accessibility testing
Security testing
API testing

QA Technologies used

Share this case

Looking for reliable Software Testing company?

Let's make a quality product! Tell us about your project, and we will prepare an individual solution.