How To Run jUnit Tests


The most preferable OS is Linux. We prefer Debian-based distros, like Ubuntu.

To run the project's jUnit tests the gcc-mips-linux-gnu package should be installed. Create MIPS64_TCHAIN environment variable that points to a directory, that contains the bin subdirectory with the toolchain components.

Install the packages that are mentioned in QEMU4V emulator's Installation Guide, because QEMU4V is used in testing.


The MicroTESK for MIPS project's Git repository contains a number of JUnit tests. The typical JUnit test contains the following sequence of stages:

  1. Template-based test program generation - the result of this stage is *.s MIPS assembly file and a *.log execution trace file;
  2. Test program compilation - the result of this stage is a binary ELF image of the test program;
  3. ELF image emulation on QEMU - the result of this stage is a *-qemu.log execution trace file.

    In the nearest future the one more stage will be added:

  4. Execution trace comparison - the *.log MicroTESK trace and the *-qemu.log QEMU4V execution traces will be compared by the Trace Matcher tool, a report will be generated.

To run the project tests, enter the project directory that contains the gradlew script, and do the following:

./gradlew clean test

Updated by Sergey Smolov 8 months ago · 12 revisions