Mirage OS vs unittest

There are more than 100 libraries compatible with MirageOS available and more are being developed everyday.

What MirageOS does in simple terms is to provide only the minimal needed for an app to run. It provides only the required network and hardware drivers needed to execute.

Using this approach it minimizes the attack surface for potential hackers since they don't have any shell to log into or any other insecure cruft that other deployment methods, such as full operating systems have.

PyUnit has been a part of the Python standard library since version 2.1 as the unittest module. This makes it widely available to developers without the need to install additional modules since it's coming out of the box with Python.

The way tests are run is through:
if name == 'main':
unittest.main()

Then unittest.main() builds a TestSuite object that contains all the tests that have method names starting with "test", then a TextTestRunnerwhich then executes each method and prints the results.

But individual test cases can be executed simply by specifying their names on the terminal:

python unittest_program.py testProgram.testGetFeedPostingHost

The default output is usually pretty concise, but it can be more verbose simply by adding a -v flag in the end when calling the test from the command line.

So unittest can be considered pretty flexible when it comes to test case execution.

Since pyUnit is a derivative of xUnit and it's quite similar to other xUnit frameworks, it's quite easy for people with not much Python background to relate to.

Unittest reports tests duration in milliseconds