Skip to content

Latest commit

 

History

History
15 lines (13 loc) · 2.05 KB

SmokeTesting.md

File metadata and controls

15 lines (13 loc) · 2.05 KB
Raw

General steps to follow for producing Smoke Tests

These are the general steps to execute the Smoke Tests found in/test/functional/buildAndPackage on your local machine. They are run using the same mechanisms as the AQA test suite, with the TestKitGen (TKG) harness that provides a standardized way to deal with these tests under automation.

  1. Ensure test machine is set up with test prereqs
  2. Build or download/unpack the SDK you want to test to /someLocation
  3. export TEST_JDK_HOME=/someLocation // set test JDK home. On windows, the windows path format is expected. (i.e., TEST_JDK_HOME=C:\someLocation )
  4. git clone https://github.com/adoptium/aqa-tests.git to /testLocation
  5. cd aqa-tests
  6. ./get.sh --vendor_repos https://github.com/adoptium/temurin-build --vendor_branches master --vendor_dirs /test/functional
  7. ( When running get.sh ensure the vendor parameters are passed correctly, the above example shows how to run the smoke tests contained within the temurin-build repository )
  8. cd TKG
  9. Export environment variables suitable for the SDK under test and for the test materials being used (i.e., export BUILD_LIST=functional/buildAndPackage, this value details which test material that should be compiled.
  10. make compile // fetches test material and compiles it, based on build.xml files in the test directories
  11. make _extended.functional // executes the test target (can be test group, level, level.group or specific test). i.e., openjdk (all tests in openjdk group), sanity.functional (all functional tests labelled at sanity level), or in the case of smoke tests which are all tagged to belong to level=extended and group=functional, we use _extended.functional and because we have limited BUILD_LIST to the directory where the smoke test material lives, we will only run tests from that directory tagged as extended.functional.