Before I started at DOUGLAS, one question was constantly buzzing through my head: How does a new UI element get into the online store? Now I can explain it to you.

Once the feature planning has been completed in a roadmap, the design is conceived by our colleagues in the UX department and worked out as a Figma prototype. If there are several different ways to implement the same user story, A/B tests may also be conducted during this phase to determine the best variant. After the finished design has been handed over to us devs for development, we begin to work until the keys glow!

And here comes the magic. Because as soon as a feature has been implemented, the deployment process starts.

With each pull request, an automatic build process is performed that checks the code quality and runs unit tests with Jest on each individual component. If all goes well here, a push of a button is all it takes to start the Azure pipeline, which installs a dedicated test server where we and the QA team can rigorously test the developed feature. In many cases, this includes end-to-end testing with Playwright. This tool automatically clicks through the store and reports on potential bugs and quality defects that we missed during manual testing. It makes my developer heart beat faster! For testing purposes, we also have the ability here to create dedicated test data such as products with special features via IMPEX Builder. This rigorous test track gives me as a developer the assurance that my features are robust and free of bugs.

Categories

ProductCamp Berlin 2023

Tech, Teamwork and Innovation

WeAreDevelopers 2023 – Part 2

WeAreDevelopers 2023 – Part 1

From Design to Deployment – How the UI is Created in the DOUGLAS Online Shop

Laura’s DOUGLAS Journey: From Trainee to Head