Aditi Joshi and Sam ParkSoftware engineersAudible
Audible Java services. Engineers generated tests and ran code transformations with Q in the IDE, and a person reviewed every generated test.
AWS DevOps Blog, published Read the case study (opens AWS DevOps Blog in a new tab)
Observation
Audible engineers used Amazon Q Developer to write unit tests one method at a time and to move a large Java test suite to JUnit 5.
- Takeaway
- Point Q at one method at a time with explicit edge cases to cover, review every generated test, and finish transformation jobs before the April 30, 2027 end of support.
- What happened
- Audible engineers asked Q for tests on individual Java methods and reviewed each suggestion. Requests covered edge cases, error handling, and exceptions. The team reports comprehensive unit coverage across more than 10 key packages and about an hour saved per class of 8 to 10 tests. It migrated more than 5,000 tests from JUnit 4 to JUnit 5. Q transformation saved over 50 hours on a JDK 8 to JDK 17 migration.
- Vendor case study (AWS DevOps Blog, co-written by Audible engineers)
- Team-reported figures
- No model named
Deployment details
Audible Java services. Engineers generated tests and ran code transformations with Q in the IDE, and a person reviewed every generated test.
- Vendor case study (AWS DevOps Blog, co-written by Audible engineers)
- Team-reported figures
- No model named
- Team
- Audible engineering teams working on Audible across Amazon platforms
- Workload
- Unit test generation for Java classes, JUnit 4 to 5 migration, and a JDK 8 to 17 upgrade
- Product version
- Amazon Q Developer in the IDE: chat, test generation, and code transformation
- Measurement
- Packages covered, tests migrated, and hours saved, as the team reported them, with no counting method described