@@ -130,14 +130,14 @@ You can access any of the model fields in the template, and make changes accordi
130
130
- This one is usefull if you are stuck on a problem, your solution gets ` WA ` and
131
131
you can't figure out a testcase that will make it break.
132
132
- If you know how to write a brute force solution to the problem, egor can help
133
- with running the that solution that you know gives the correct answer against
133
+ with running the solution that you know gives the correct answer against
134
134
your (optimal) solution, and figure out when will they differ.
135
135
136
136
### Steps to make a batch test
137
- - Create a batch configuration
137
+ - Create a batch directory structure:
138
138
139
139
```
140
- egor batch create --has-brute
140
+ egor batch create
141
141
```
142
142
143
143
Running this will create 3 additional files:
@@ -153,12 +153,14 @@ Running this will create 3 additional files:
153
153
Once all the files are filled according to their purpose, you can start running
154
154
your batch test using
155
155
156
+ - Run the batch test:
157
+
156
158
```
157
- egor batch run --tests=10
159
+ egor batch run --tests=100
158
160
```
159
161
160
162
the parameter ` --tests ` tells egor how many times it should run your code,
161
- a ` 100 ` is a good start.
163
+ a ` 100 ` is a good start (and it's the default) .
162
164
163
165
If you can't find a failing testcase after this, you can increase the
164
166
` --tests ` parameter, or change the generation strategy, (ex: try bigger
0 commit comments