Jasmine Test Runner

A : Yes! All settings for the plugin are configured with the ‘jasmine_test_runner’ WordPress filter.

This shows an example of adding specific unit tests that your plugin would run if a user has Jasmine Test Runner enabled. This will load a set of unit tests located in a plugin’s /tests/ directory.

function add_unit_tests( $settings ) { $files = array(); foreach ( glob( __DIR__ . '/tests/*.js' ) as $filename ) { $file = basename( $filename ); $files[] = plugins_url( "tests/{$file}", __FILE__ ); } $settings['tests'] = array_merge( $settings['tests'], $files ); return $settings; } add_filter( 'jasmine_test_runner', 'add_unit_tests' );

A : Definitely! You may want to have the test runner load everytime on a certain page or section the admin, so this is an example of overriding that setting as well. This will load the Jasmine test runner on a page called ‘toplevel_page_boldgrid-inspirations’.

function load_inspirations_jtrunner( $settings ) { $settings['loads_in'] = array_merge( $settings['loads_in'], array( 'toplevel_page_boldgrid-inspirations' ) ); return $settings; } add_filter( 'jasmine_test_runner', 'load_inspirations_jtrunner' );

A : This can also be done, but keep in mind that running it all the time, and having multiple tests running can cause negative performance impacts. This code forces Jasmine Test Runner to always run in admin:

function force_load_jtrunner( $settings ) { $settings['loads_in'] = array( 'all' ); return $settings; } add_filter( 'jasmine_test_runner', 'force_load_jtrunner' );

A : Jasmine Test Runner can run the tests in random order by adding &random=true to your query string.

A : The seed number and seed URL are displayed in the Jasmine Test Runner status bar when you’ve selected to run random or a seed. For failed tests the bar appears red. If you need to obtain this seed programatically, .jasmine-seed-bar class contains the link to run the seed, and the link text is the seed number.

A : If you wish to use your own seed generatator algorithm, you can specify the resulting seed directly by appending &seed=YOUR_SEED. Where YOUR_SEED is, should be the resulting seed you’ve generated.