Coding Challenge Engine

Simple framework to develop and debug coding challenge solutions.

This project aims to help the development of solutions for challenge websites like
CodinGame
HackerRank

Currently, it supports only C++, but Python is coming soon. Feel free to request any other language support. :)

Features

• Check solution code against test cases
• Report results
• #2 Time measurement
• Select test/tests to run
• Rerun test case/cases for a given number of times
• DebugPrint that does not affect the solution output
• Unit test the solution code (Google Test?)
• #1 Automate solution code generation (do not have to edit solution class by hand, a script generates the final version that can be submitted)

Engine usage

1. Add the test case to the test-cases folder (e.g. src-cpp/test-cases).
2. Add your solution to Solution::SolutionSourceCode().
3. Build and run the project and see the output.

Test file

You can add multiple test cases to the test cases folder.
You can run all the tests by calling Runner::InitWithAll().

TestRunner Runner;
Runner.InitWithAll();
Runner.RunTests();
Runner.EvaluateSolution();

Or you can run one or multiple test cases by calling Runner::InitWithFileNames( { "test0.txt" } ).

TestRunner Runner;
Runner.InitWithFileNames( { "test-case-0.txt", "test-case-1.txt" } );
Runner.RunTests();
Runner.EvaluateSolution();

The solution runner only reads two sections:

• Between TEST_START and TEST_END.
• Between SOLUTION_START and SOLUTION_END.

Data input and output

The engine is communicating via stdin and stdout. In Solution::SolutionSourceCode() stdin and stdout are redirected so its behavior is equivalent to most of the challenge websites.

Test file structure:

You can add comments here or to any other part that is outside the sections.

Input data:
1st line: 1 positive integer n
n lines of integers

Output data (the solution):
n lines with the input data multiplied by 2

TEST_START
4
2
-3
0
9
TEST_END

SOLUTION_START
4
-6
0
18
SOLUTION_END

Time Measurement

You can measure the running time of the solution. Two default time points are added: start, end. In Solution.cpp you can add a new time point as below:

// Context is a pointer to TestRunner instance
// Input parameter is the time point's name
Context->AddTimePoint( "User Defined" );

After every test case evaluation, there is a timetable with the time point names and the absolute and relative time points.

                         Absolute Time    Relative Time
Start                          0.000 s          0.000 s
UserDefined1                   0.014 s          0.014 s
UserDefined2                   0.021 s          0.007 s
End                            0.110 s          0.089 s