This gives us enough time to begin planning test cases and build out the foundation for any test automation we’ll use to validate the new product or feature. When following this concept of testing, we meet with the Development and Product Management teams early on to become familiar with the new product or feature, including any user experience requirements. Instead of testing the product toward the end of development, we shift the testing left in the schedule and continuously plan, build, and run tests throughout the cycle. Shift Left is a testing concept used to avoid bottlenecks and delays. This traditional schedule of testing can create bottlenecks, and can even lead to delays in a product’s release. This can lead to multiple problems, especially if several issues are found with the product this late in the cycle.
SONOS SOFTWARE DEVELOPMENT ENGINEER IN TEST SOFTWARE
Traditionally in many software development models and strategies, testing the product is pushed near the end of the development cycle. We work in tandem with our Development team during the development cycle for any new feature or product, and because of this we naturally fall into a Shift Left testing practice. When we build a new feature for the Sonos system, we target each step of our Quality Assurance (or QA) process. We maintain a high bar for quality so that users consistently have delightful interactions with their Sonos system, especially when it comes to new features or products. Each interaction a user has with our system gives us a chance to delight them, but if we don’t meet our quality bar, this interaction can lead to frustration.
As with all user interactions and experiences, any hiccup can seriously tarnish the opinion of the brand. When developing a new feature or product for the Sonos system, we take the quality of our hardware and software very seriously.
0 kommentar(er)
