Results for fas_test

Provide feedback for Fedora updates (inspired by fedora-easy-karma)

Activity reporting for Fedora, EPEL, and CentOS SIG packaging work

It has been created for personal blog creation purpose. Timus has its limits, but it fulfills the purposes for which it was created.

Fast TUI toolkit for viewing, translating, and manipulating biological sequences.

Build dependency resolver — compute build order for cross-branch package porting

Build phylogenomic datasets in seconds.

Batteries Included Text Based Application Framework

Batteries Included Text Based Application Framework

Download and analyze U.S. appropriations bills from Congress.gov

Auto-discovers test classes in the working directory and runs the tests with<br/><br/>basically no boot up time and no configuration. It doesn't matter how you<br/><br/>structure your project, instead, simple naming conventions are used:<br/><br/><br/><br/> - All test files should be named *_tests.rb<br/><br/> - All test methods should be named test__*<br/><br/><br/><br/>Other things you need to know:<br/><br/><br/><br/> - All test classes should inherit FasTest::TestClass<br/><br/> - There are two setup and two teardown methods:<br/><br/> - class_setup: Called once before any of the tests<br/><br/> - class_teardown: Called once after any of the tests<br/><br/> - test_setup: Called before each test<br/><br/> - test_teardown: Called after each test<br/><br/><br/><br/>Take a look in the test folder to see an example of how the library is used.<br/><br/>(fas_test is used to test itself).<br/><br/><br/><br/>To actually run your tests just invoke fastest.rb from a command line. It will<br/><br/>automatically recursively discover all of your test classes within the working<br/><br/>directory and run there tests.