User Tools

Site Tools


Sidebar

projects

dsi0 (20180822)
wcp1 (20180822)
ael0 [faq] (20180829)
wcp2 (20180829)
sln0 [faq] (20180905)
wcp3 (20180905)
sln1 [faq] [metrics] (20180912)
wcp4 (20180912)
sll0 [faq] [metrics] (20180919)
wcp5 (20180919)
sll1 [faq] [metrics] (20180926)
wcp6 (20180926)
sll2 [faq] [metrics] (20181003)
wcp7 (20181003)
sll3 [faq] [metrics] (20181017)
sll4 [faq] [metrics] (20181017)
wcp8 (20181017)
dln0 [faq] [metrics] (20181024)
dll0 [faq] [metrics] (20181024)
wcp9 (20181024)
dll1 [faq] [metrics] (20181031)
wcpA (20181031)
dll2 [faq] [metrics] (20181107)
dls0 [faq] [metrics] (20181107)
wcpB (20181107)
dlq0 [faq] [metrics] (20181115)
wcpC (20181115)
dlt0 [faq] [metrics] (20181128)
EoCE (20181213-172959)
haas:fall2018:data:projects:ael0:faq

AEL0 FAQ

projeval tests aren't passing, is this important?

I plan to use projeval when I evaluate your project (since it nicely automates so many important tests I'd otherwise have to do by hand), so yes: it is rather important.

Be sure you are conforming to project specifications! All things that need to output to STDOUT vs. STDERR.

What is going on in a specific projeval test?

projeval test data is located under /usr/local/etc/eval (additional directories for course desig and project therein).

Eventually there will be directory names by the number of each test, and inside will be four files:

  • args.txt: additional arguments appending to the command-line when running your program
  • desc.txt: description of the test (likely what you see on projeval output)
  • in.txt: program input sent into your program at runtime (STDIN redirection)
  • out.txt: program output that is expected (when program is run with args and input sent in; usually the very last line of output)
haas/fall2018/data/projects/ael0/faq.txt · Last modified: 2017/08/28 16:42 by 127.0.0.1