Abstract:
With the arrival of new function comes new bugs and new bug fixes. Therefore it is critically important to regularly run existing tests ( to check for regressions) , as well as new tests. Deciding what to run and how frequently to run it needs to be carefully considered, especially when it is not feasible to run all tests on every build. Testing the IBM Java SE product is a larger task that you may expect - To the casual user it is a black box that provides you with a base on which to run your Java applications, but peek beneath the surface and you find a complex combination of systems including not only the core VM, but also a JIT compiler, Garbage Collector, base Class Libraries as well as bundled value add libraries. Coupled with the wide range of platforms supported and the geographical spread of the development teams the challenge facing the test teams is high.This talk focuses on how implementation of Java is tested across a worldwide organisation in an Agile development environment. The focus will be on the high level of automation required to support continual verification across a wide and disparate set of platforms (including AIX, Linux (x86, Power and zSeries), Windows and z/OS ) and how to efficiently handle the triaging, debugging and defect raising for tests that fail.