Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Tool for automatic testing and creating problems from
Branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.



jtest is a command-line tool designed to improve your productivity when solving problems from

jtest provides some simple commands to finding new problems and creating workspaces to solve them. Also, jtest can compile and test your “solutions” with the public samples of the problems.


jtest is avaliable in RubyGems. To install it type:

gem install jtest


Finding a problem

$ jtest find Treasures
working  Trying to find problems that match: Treasures
 P70690  Treasures in a map (1)
 P60796  Treasures in a map (2)
 P90766  Treasures in a map (3)
 P39846  Treasures in a map (4)
  found  4 matches found!

This will show all the problems that contain `Treasures` in his name!

Creating a new problem

Let's create a workspace for solving `Treasures in a map (1)`.

$ jtest new 70690
connecting  Getting info about problem P70690_en...
     found  P70690_en: Treasures in a map (1)
   working  Creating workspace for P70690_en: Treasures in a map (1)
    create  P70690_Treasures_in_a_map_(1)
    create  P70690_Treasures_in_a_map_(1)/sample1.dat
    create  P70690_Treasures_in_a_map_(1)/sample1.out
    create  P70690_Treasures_in_a_map_(1)/sample2.dat
    create  P70690_Treasures_in_a_map_(1)/sample2.out
    create  P70690_Treasures_in_a_map_(1)/sample3.dat
    create  P70690_Treasures_in_a_map_(1)/sample3.out
    create  P70690_Treasures_in_a_map_(1)/

As you can see, jtest automatically downloads every public sample of the problem and creates a C++ main file to start solving your problem.

Testing your solutions

All right! I think I've solved the problem we created before. Let's see if it passes the public samples!

$ jtest test
testing  Running tests on P70690_Treasures_in_a_map_(1)...
compile  P70690_Treasures_in_a_map_(1)/
running  P70690_Treasures_in_a_map_(1)/sample1.dat
  wrong  P70690_Treasures_in_a_map_(1)/sample1.out
running  P70690_Treasures_in_a_map_(1)/sample2.dat
  wrong  P70690_Treasures_in_a_map_(1)/sample2.out
running  P70690_Treasures_in_a_map_(1)/sample3.dat
  wrong  P70690_Treasures_in_a_map_(1)/sample3.out
 failed  0
missing  0
  wrong  3
 passed  0
  total  3

Ooops! It seems my solution doesn't work very well… When the Nth sample test fails jtest saves the output of your solution as sampleN_test.out in the problem's workspace, so you can see what's going wrong.

Getting help

You can obtain help about how to use one command with the help command. For example:

$ jtest help new

Will show you all the information you need to use the `new` command (syntax, options, description, etc.).

Contributing to jtest

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.

  • Fork the project.

  • Start a feature/bugfix branch.

  • Commit and push until you are happy with your contribution.

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.


Copyright © 2012 Héctor Ramón Jiménez. See LICENSE.txt for further details.

Something went wrong with that request. Please try again.