An Open-source Product Testing Makeover
Here we intend to share a story of our evolution which made our product testing in opensource more adoptable, less complex with reduced cost and turnaround time.
In-house Vs opensource product
When products move from in-house to open, the challenges associated with testing such products are less predictable. An in-house product has mostly a known set of customers with a specific pattern of usage which helps the product team design the various testing scenarios.
However, once the same product is open-sourced, a wider range of customers and usage scenarios exist, exercising the product in new ways. This new market of customers and the potentially new ways they will use the product brings several challenges. It requires an understanding of whether the existing testing is good enough or it requires enhancements. If enhancements are required, then how to handle them with existing resources?
Makeover story
This presentation addresses the makeover story from the perspective of Eclipse OpenJ9 at AdoptOpenJDK , particularly: -
- challenges involved with the in-house (third-party tools) tooling & testing, such as
- Tests spread across multiple repositories
- Adding tests in CSV’s in specific format, located in a specific repository
- Changing wrappers and variables located in a different repository
- Maintaining multiple versions of tests
- Building local sandbox for tests & wrappers, testing them and then commit the changes in repository.
Do they look challenging, time consuming and a bit of manual in nature? Same will be explained in detail during the presentation.
iI) how OpenJ9 opensource testing was enhanced to make it more adaptable towards the open-source third-party tools and products?
Our presentation will shed light on how these enhancements were achieved using git, docker and Jenkins. A demo from us will make it easier to understand.
iii) how the test enhancements were achieved with reduced cost and complexity.
We will present on how these enhancements were done using our opensource Jenkins test framework.
While the open testing story is still evolving, the initial benefits of the much-needed makeover far outweigh the costs and serve as an example to inspire improvements and innovation for those facing similar challenges.