Overview
Arlo is a global technology leader in wireless surveillance cameras, doorbells and smart lighting. Like many companies using Oracle Cloud solutions, they were challenged by quarterly updates taking up time and resources.
Problem
Oracle provides quarterly updates to its customers, requiring mandatory testing before moving to production. The testing window is short, creating the need for an automated solution. Arlo were challenged by quarterly updates taking up valuable time and resources.
- Mandatory testing before every quarterly Oracle Cloud update
- A short testing window consuming valuable time and resources
- Test data rebuilt from scratch at every upgrade
Preparing test data ahead of each quarterly upgrade was repetitive work that consumed the team before testing had even begun.
Approach
Winfo’s automated testing solution, WinfoTest, provided a pre-loaded Test Script Library integrated with SharePoint. Test data was prepared one time for all test scripts, saving Arlo from repetitive set up at each quarterly upgrade.
- Employee Self-service
- Manager Self-service
- Administration
- Talent Management
- Compensation Management
- Pre-loaded Test Script Library integrated with SharePoint
- One-time test data preparation reused every quarter
On top of the 2,000+ pre-loaded test scripts available in the WinfoTest library, Arlo were easily able to add an additional 10% of client-specific scripts using the Script Assistant.
Outcome
Arlo now complete their test cycle in just two days, quarterly updates are fully tested, and bugs are caught early before go-live, reducing testing costs for their Oracle Cloud application by 80%.
“We were able to complete the testing cycle in just 2 days, the user experience is intuitive, and the performance is good. It reduced our testing cycle to one and business has to just validate the reports and sign off.” — Swapna Pallapinti, Director of IT, Arlo
Before vs After
The Difference Automation Makes
Manual Process
- Repetitive test data set up each quarter
- Full quarter of testing effort
- Incomplete upgrade coverage
- Bugs surfacing late
Automated Workflow
- Two-day test cycle
- 250+ scripts executed quarterly
- 80% lower testing time and costs
- Bugs caught before go-live