Played Challenges
Reconstruct the actual output from my unit test tool report - 152 entries
When a test fails, my unit test tool reports differences between the actual output and the expected output as follow: - line in the expected output but missing in the actual output are prefixed with a dash - unexpected lines in the actual output are prefixed with a plus sign - comments added by the unit test tool are prefixed with a question mark - common lines are showed `as-is` (well, almost;) From that "diff" format, I would like to reconstruct the actual output.
- Best score: 16
- Best player score: 17
- Position: #28 / 52
- Number of attempts: 2
prepend * to every non-blank line - 6304 entries
Prepend an asterisk to every non-blank line in the input file.
- Best score: 10
- Best player score: 10
- Position: #42 / 1536
- Number of attempts: 4
One number per line - 18722 entries
Just give me the numbers.
- Best score: 14
- Best player score: 14
- Position: #639 / 3860
- Number of attempts: 8
Add semicolons - 10848 entries
Simply add a semicolon at the end of each line
- Best score: 10
- Best player score: 10
- Position: #488 / 3061
- Number of attempts: 5
Split line with dots - 2144 entries
This line is too long, split it.
- Best score: 15
- Best player score: 15
- Position: #154 / 634
- Number of attempts: 7
Box it - 7902 entries
Create a box around a line.
- Best score: 21
- Best player score: 21
- Position: #313 / 1874
- Number of attempts: 8
JSON string rotation - 64 entries
Right value strings are misplaced. Just rotate them! I'm too kind with you guys and didn't included "strings with \" in it"!
- Best score: 19
- Best player score: 19
- Position: #6 / 22
- Number of attempts: 11
Collect List - 4298 entries
Convert to comma separated list.
- Best score: 12
- Best player score: 12
- Position: #471 / 1190
- Number of attempts: 5
Contributed Challenges
Reconstruct the actual output from my unit test tool report - 152 entries
When a test fails, my unit test tool reports differences between the actual output and the expected output as follow: - line in the expected output but missing in the actual output are prefixed with a dash - unexpected lines in the actual output are prefixed with a plus sign - comments added by the unit test tool are prefixed with a question mark - common lines are showed `as-is` (well, almost;) From that "diff" format, I would like to reconstruct the actual output.
Sylvain Leroux / Yes, I Know IT !
Twitter: @Yes_I_Know_IT
Sylvain Leroux. Engineer by Passion, Teacher by Vocation. My goals : to share my enthusiasm for what I teach