This has a hidden (dot-prefixed) bash file which will return some sort of result with both string information about performance, and a percentage based on performance.
I want these tests to be compatible with existing tools (i.e. python3 -m unittest) so this design should be hashed out in order to make sure we're creating the best, most flexible interface for executing and evaluating arbitrary code. However, I like having the code in the github repository, because the user can evaluate their own code, and professors can share these repository skeletons in order to create less work in making tests (i.e. a professor could come up with a computer organization repository set which does tests for all of their comp org assignments, and these could be shared among many professors by simple forking).
Another idea-- some parameter which goes into the bash file to specify which assignment (so the repository can be used for all assignments in a class, not just one assignment at a time).
@clararichter @abebinder [I don't know Russell's tag] I would love any feedback you have on this design choice, or any better way you think we should go about this.
nasonfish
commented
5 years ago
This is for any discussion regarding what a test should look like. During a meeting last week, I threw out a design which can be seen here:
https://github.com/nasonfish/derp-test
This has a hidden (dot-prefixed) bash file which will return some sort of result with both string information about performance, and a percentage based on performance.
I want these tests to be compatible with existing tools (i.e. python3 -m unittest) so this design should be hashed out in order to make sure we're creating the best, most flexible interface for executing and evaluating arbitrary code. However, I like having the code in the github repository, because the user can evaluate their own code, and professors can share these repository skeletons in order to create less work in making tests (i.e. a professor could come up with a computer organization repository set which does tests for all of their comp org assignments, and these could be shared among many professors by simple forking).
Another idea-- some parameter which goes into the bash file to specify which assignment (so the repository can be used for all assignments in a class, not just one assignment at a time).
@clararichter @abebinder [I don't know Russell's tag] I would love any feedback you have on this design choice, or any better way you think we should go about this.
Thanks!