In the company where I work there are 3 products: software, application and site - each with a different QA process. The question is how would you suggest integrating the QA process in different scenarios? Because there are tasks in which the QA man checks the task and there are those who "created" the task and checked whether it was indeed done at his request.
As a QA Manager, I've been requested to train my wider team that includes Product owners, business analysts to train them in software testing that's relevent so they can lend a hand as my team has been significantly reduced due to losses.
Any strategy you could suggest or guidelines to how to go about it will be helpful please?
Today’s mobile behaviors and expectations have radically changed, a result of the continuous evolution of mobile technology and the myriad new ways users can now interact with mobile. Because of this advancement in technology and user behavior, testing organizations must also advance their mobile testing solutions to ensure they continue to deliver the most intuitive, up-to-date experience possible.
As companies continue to embrace the mobile-first strategy, many are grappling with a formidable challenge: how to release mobile updates more frequently given the painful and archaic app publishing process. Beyond brute-forcing release cadence, there need to be cultural, technical, and infrastructural changes to make frequent releases a reality. Stacey Yan and Alex Cabanilla will explore these dimensions in depth and provide practical insights on how to boost build infrastructure and reduce build time, improve code quality and merge process and guard against bad code, manage mobile features through feature toggles, improve test automation and make tests less flaky, and leverage critical tests. They'll also detail the key elements necessary for a culture of frequent releases. You'll come away with actionable ideas on ways to improve large-scale mobile delivery and CI/CD practices to enable frequent releases.
In this interview, Amir Rozenberg, director of product management at Perfecto Mobile, says the success of a business depends on taking advantage of web apps that improve and simplify the customer experience, addressing options that will yield a successful implementation.
The definitive features of a mobile social app are the ability to send and receive messages, push notifications, and sharing media such as photos, audio, and videos. While creating a test strategy for such apps, cross-platform compatibility is an important consideration. Here are some scenarios you should include in your test strategy for a social media mobile app.