The modernization of software into cloud-based services has become an integral part of business transformation, enabling organizations to leverage the scalability and flexibility offered by the cloud. In this context, Eclipse AQAvit, a project under the Eclipse Adoptium banner, aims to facilitate the verification of Java SE and related technologies, specifically focusing on testing in cloud-based environments.
The Eclipse Foundation provides a fairly large CI/CD farm to Eclipse projects to help them deliver well tested software with a fast build cadence. Maintaining and supporting a wide variety of CI instances is a challenge, but also gives a unique insight to build processes. This insight helps to establish best practices that make continuous integration and delivery more reliable and robust. We will share those best practices, talk about common issues and how they can be avoided.
Open AQAvit Test Strategy for OpenJDK binaries are based on open, transparent, robust, and adaptable test suites. We are establishing AQA as the comprehensive open quality standard for OpenJDK verification. AQAvit verification demonstrates that the product is a high-quality offering, ready for enterprise usage, and production quality inclusion criteria. It is one of the three requirements for listing at the Adoptium Marketplace.
How does a testing team approach an Open Source project? There are two ways to do it: a reactive and a proactive approach.
In this talk we would like to present our proactive approach executed in the Oniro project and the beneficial effects that this approach gives to the product. We will compare this methodology with the reactive one and how it will improve the overall project quality.
This talk shall target Project Managers, Team Leaders and V&V People.
Over the past few years, Kubernetes has matured enough to be the favorite application orchestration platform i.e. Cloud Native (Java) Application platform, but it still missed one crucial feature of in-cluster build and deploy of the applications. The missing feature made the continuous integration and deployment(CI/CD) to be less effective on Kubernetes based platforms. The market had various solutions to solve the problem but 99% of the solutions missed something — being “Kubernetes Native” and naturally built for “K(C)loud Native Applications”.
