Testing strategies for the eCommerce stores built on Magento
3 likes942 views
This document discusses the importance of software testing for e-commerce stores, emphasizing its impact on customer success and revenue. It covers common bug types, challenges in agency testing environments, and best practices for good engineering, project management, and testing strategies. The author highlights the need for contextual understanding and reusable knowledge in testing processes to improve quality and client satisfaction.
Testing strategies for the eCommerce stores built on Magento
- 1. Anand Ramdeo MD - EMEA Region [email protected] @testinggeek Testing Strategies for the eCommerce Stores built on Magento
- 2. Introduction
- 3. The only way to grow is By making our customers successful
- 4. Software Testing - A Key Driver for the customer success
- 5. Common Bug Types - eCommerce Store Big and Visible - Server Error - 404 - Service not available Small & Neglected - Layout and interaction errors - Third party integration - Usability issues
- 6. Impact of software defects on the bottom line ● Lost revenue ○ Will not wait for the page load ○ Will abandon the shopping process ● Lost opportunity ○ Will not trust your site ○ May never come back, Will go to the competitors ● Bad publicity ○ Will tell the world about the bad experience Users are impatient, unforgiving and connected
- 7. Impact of software defects on development New Features Enhancements Channels Defects and issues that customer found How do you spend most of your time?
- 8. Challenges of testing in an Agency environment Conflicting Priorities - Work is driven by the client’s preferences. - Conflicting priorities between PM, AM, and the testers.
- 9. Good Engineering Practices - Our survival kit ● Communication & Clarity ○ Understand the business, vision, and the rationale. ● Clean code and good architecture ○ DRY, YAGNI, KISS, SOLID and other relevant principles. ● Development processes ○ Unit testing, code review, Static analysis, functional automation and manual testing. ● Project Management ○ Scrum, Kanban, Transparent, and accountable. ● Skills assessment and path ○ Where do we stand and how do we get better? ● Knowledge Management ○ Utilise the domain and functional expertise of the whole group to help the client.
- 10. Testing Strategies - How do we test? ● Contextual ○ Every project, team, and assignment is different. Understand first, suggest later. ● Repeatable ○ Process driven, supported by tools and mentors. ● Robust ○ Accountable, visible, and trustworthy reports. ● Extensive ○ Beyond GUI and with focus on NFT such as security, usability, accessibility, performance etc. ● Reusable ○ Automation, checklists, guidelines, data, test scenarios ● Prepared ○ Monitoring and continuous testing on production.
- 11. What do we test? - Common Features
- 12. Testing Knowledge Base - APIs and Integrations Paging Authentication Parameters Authorisation Security Behave Error Handling State Filter Order Diagnostic Versioning Logging Accessibility Purpose Consumer Domain specific names, Examples, easy-to-learn, documentation, hard-to-misuse, easy-to-use, lead to readable code, principle-0f-least astonishment, guessability, and consumability https://www.linkedin.com/pulse/testing-restful-webservices-api-remember-papas-sfo-deed-ramdeo/
- 13. Where do we test? - Devices & Browsers Compatibility ● Responsive by default ● Driven by analytics - what devices and browsers your users would be using? ● On the lines of graded browser support
- 14. Testing Knowledge Base - Few examples - Search High level test ideas and reusable test scenarios
- 15. Testing Knowledge Base - Few examples - Shopping cart, communication etc. Mindmap - Our most important testing tool
- 16. NFT, Monitoring, or A/B Testing - everything is covered! Happy to share the full mindmap. Send me an email
- 17. Summarise ● Testing is important, it affects the bottom line. ● Small defects related to layout, interaction, and usability are as damaging as the big ones. ● Good engineering practices could be the most important factor in improving quality. ● Your project and its context is unique - consider that before adopting any solution. ● Do not reinvent the wheel, use the knowledge that is available. ● Be proactive and make your clients and organisation successful.
- 18. Thank You - For your time and attention. Any Questions? Anand Ramdeo MD - EMEA Region Email : [email protected] Twitter : @testinggeek LinkedIn : https://www.linkedin.com/in/anandramdeo/ Let’s Stay Connected.