testrus 0.0.2 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.md +20 -14
- data/lib/testrus/version.rb +1 -1
- metadata +1 -1
data/README.md
CHANGED
|
@@ -2,24 +2,30 @@
|
|
|
2
2
|
|
|
3
3
|
Aids in testing your programs in informatics competitions.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Install it with `gem install testrus`.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## Usage
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
`testrus` looks for input and output file pairs in the directory you run it
|
|
10
|
+
from. E.g. if:
|
|
10
11
|
|
|
11
|
-
|
|
12
|
+
```bash
|
|
13
|
+
$ ls
|
|
14
|
+
input.1
|
|
15
|
+
input.2
|
|
16
|
+
output.1
|
|
17
|
+
output.2
|
|
18
|
+
```
|
|
12
19
|
|
|
13
|
-
|
|
20
|
+
You have two tests. The expected output is in the output file. To test your
|
|
21
|
+
program, simply run testrus from this directory with the command to run your
|
|
22
|
+
program, then the test data will be piped to your program via STDIN.
|
|
14
23
|
|
|
15
|
-
|
|
24
|
+
If the runtime exceeds a second or the memory usage ever exceeds 64mb the test will
|
|
25
|
+
also appear failed.
|
|
16
26
|
|
|
17
|
-
|
|
27
|
+
## Screenshots
|
|
18
28
|
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
2. Create your feature branch (`git checkout -b my-new-feature`)
|
|
23
|
-
3. Commit your changes (`git commit -am 'Add some feature'`)
|
|
24
|
-
4. Push to the branch (`git push origin my-new-feature`)
|
|
25
|
-
5. Create new Pull Request
|
|
29
|
+
|
|
30
|
+
|
|
31
|
+
|
data/lib/testrus/version.rb
CHANGED