Full-Stack Development and Quality Assurance for a Marketing Content Platform
Challenge
Brandgility operates a marketing content platform that is continuously evolving, with new functionality being added and the user base growing over time. This required the product team to scale its engineering and QA capacity while maintaining a high level of product quality and customer satisfaction.
The initial requirement was an AQA Engineer who could establish and expand test automation. As the cooperation progressed and the platform's needs increased, Brandgility required additional expertise, including Node.js developers, frontend developers, a React Native developer, and another QA engineer.
The key challenge was scaling the team quickly without compromising the quality of development and testing. The mature platform required efficient coverage of stable functionality through automation while new and frequently changing features still needed thorough manual testing. The specialists also had to integrate into Brandgility's existing sprint-based workflow and collaborate closely with the product and development teams.
Brandgility operates a marketing content platform that is continuously evolving, with new functionality being added and the user base growing over time. This required the product team to scale its engineering and QA capacity while maintaining a high level of product quality and customer satisfaction.
The initial requirement was an AQA Engineer who could establish and expand test automation. As the cooperation progressed and the platform's needs increased, Brandgility required additional expertise, including Node.js developers, frontend developers, a React Native developer, and another QA engineer.
The key challenge was scaling the team quickly without compromising the quality of development and testing. The mature platform required efficient coverage of stable functionality through automation while new and frequently changing features still needed thorough manual testing. The specialists also had to integrate into Brandgility's existing sprint-based workflow and collaborate closely with the product and development teams.
Solution
QA Madness provided Brandgility with a combined software development and QA team, assigning specialists according to the client's required skills and experience. The cooperation initially focused on expanding the existing automated testing framework and introducing minor process improvements. As the client's needs grew, QA Madness scaled the team with additional development and QA specialists.
The team works in three- to five-week sprints. QA and software engineers participate in daily meetings and join discussions where upcoming features are presented and planned. Early QA involvement allows specialists to review requirements and contribute to feature planning before development begins.
Two QA engineers currently work on the project, combining manual and automated testing. Manual testing focuses primarily on new functionality introduced during the current sprint, while automation covers stable functionality from previous releases. Most regression and smoke tests are automated.
The development team consists of three Node.js developers, two frontend developers, and one React Native developer. Developers create new functionality, fix defects, and add tests to new code. Jenkins is used to deploy development branches to the team's server, where QA engineers verify new functionality before builds move to the development server for further testing.
QA Madness provided Brandgility with a combined software development and QA team, assigning specialists according to the client's required skills and experience. The cooperation initially focused on expanding the existing automated testing framework and introducing minor process improvements. As the client's needs grew, QA Madness scaled the team with additional development and QA specialists.
The team works in three- to five-week sprints. QA and software engineers participate in daily meetings and join discussions where upcoming features are presented and planned. Early QA involvement allows specialists to review requirements and contribute to feature planning before development begins.
Two QA engineers currently work on the project, combining manual and automated testing. Manual testing focuses primarily on new functionality introduced during the current sprint, while automation covers stable functionality from previous releases. Most regression and smoke tests are automated.
The development team consists of three Node.js developers, two frontend developers, and one React Native developer. Developers create new functionality, fix defects, and add tests to new code. Jenkins is used to deploy development branches to the team's server, where QA engineers verify new functionality before builds move to the development server for further testing.
Results
QA Madness helped Brandgility stabilize its manual testing process and establish a comprehensive automated testing workflow. With most regression and smoke testing automated, the QA team spends less time repeatedly checking stable functionality and can focus more on developing new automation scripts and testing newly introduced features.
The QA engineers place particular emphasis on functional, UI, and integration testing, covering the core functionality and usability of the platform. Manual testing is focused on new features, while automated checks provide efficient coverage of functionality from previous releases.
The development team has also expanded the platform with new functionality, including user roles for approving orders and content customization options such as language selection for templates and files.
Overall, QA Madness provided Brandgility with a scalable full-stack development and QA unit that operates as part of the client's team. The combined team supports ongoing feature development, bug fixing, manual and automated testing, and can be scaled as the platform's requirements evolve.
QA Madness helped Brandgility stabilize its manual testing process and establish a comprehensive automated testing workflow. With most regression and smoke testing automated, the QA team spends less time repeatedly checking stable functionality and can focus more on developing new automation scripts and testing newly introduced features.
The QA engineers place particular emphasis on functional, UI, and integration testing, covering the core functionality and usability of the platform. Manual testing is focused on new features, while automated checks provide efficient coverage of functionality from previous releases.
The development team has also expanded the platform with new functionality, including user roles for approving orders and content customization options such as language selection for templates and files.
Overall, QA Madness provided Brandgility with a scalable full-stack development and QA unit that operates as part of the client's team. The combined team supports ongoing feature development, bug fixing, manual and automated testing, and can be scaled as the platform's requirements evolve.