brunotest
A coursework templating and testing engine to consolidate assignment code and ensure robust assignment quality.
The idea behind this framework is that it woul allow us to write only one solution code, and then carefully work out stencil around it (in fact, have the stencil generated automatically from the solution code).
The idea on how to do this is to use Region tags in the code, and
All of the templating will be done in a __brunotest__ hidden folder (that could be gitignored). The general use case is as follows (we'll say with the fibonacci example given in examples):
- Define our stencil/chaff/solution code
- Run
brunotestto run the solution code against thetests - Run
brunotest stencilto run the compiled stencil code against thetests - Run
brunotest [chaff name]to run the compiled chaff code against thetests. - Run
brunotest allto run all of the code (solution, stencil, chaffs) against thetests.
Ideally, this would also be enhanced by a VSCode extension that could allow you to more easily see the different chaffs/stencil alongside the current document you are editing (maybe similar to how Markdown preview works).
Some other considerations/definitions for now:
- The chaff implementations will be stored in
.chafffiles, and:- Do not require all of the regions defined in the solution to be overwritten, but regions that are not specified will remain the same.
- Can (somehow?) define which tests should fail and with what values, likely at the top?
- This may be somewhat challenging because we have to incorporate failing partial tests, test names, etc.
- The stencil code will be in a single
.stencilfile in the root directory (error on multiple found).- The stencil also does not have to specify every distinct region to overwrite, but those which are not specified will be left blank.
Gradescope Autograder Specifications
The gradescope autograder, with the configuration that we use it in, has the following directory structure:
/autograder/ # Base Directory
/autograder/student # Student submission
/autograder/solution # Solution code
Metadata
Release files for brunotest 0.1.1.1687008168
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| brunotest-0.1.1.1687008168.tar.gz | 7.7 kB | Without provenance | Details for brunotest-0.1.1.1687008168.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| brunotest-0.1.1.1687008168-py3-none-any.whl | Python 3 | none | any | Details for brunotest-0.1.1.1687008168-py3-none-any.whl |
Total release size: 16.1 kB
Release files / brunotest-0.1.1.1687008168.tar.gz
| Download URL | brunotest-0.1.1.1687008168.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
890eee842fbd24719711ea2c5cb7aabe4b3bf17461dc01d907739a9cfbbbe61c
|
|
BLAKE2b-256 checksum How to use checksums |
360db70dfc46abd5ad31d7b49519d7a533ae9bf2a9b88b555103c697074d6603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / brunotest-0.1.1.1687008168-py3-none-any.whl
| Download URL | brunotest-0.1.1.1687008168-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6e216fe8f1a51fb8ef54dade116c3f2b82f7ea07f01b81e351bbb5496c9808a
|
|
BLAKE2b-256 checksum How to use checksums |
bbc8d9795a66692a5e0affbceb93636268f955330f599fa4eef1690f2f93bcbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for brunotest 0.1.1.1687008168
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.