Deliverable 4 Experience

For this post, much like my other deliverable experience posts, I will be reflecting upon the feedback we received during the presentation of our fourth deliverable.

We started by simply running the main driver of our script (runAllTests.sh). This produced an HTML output that Cameron formatted pretty well. Unfortunately, we formatted it for typical resolution on a laptop screen (I'm not sure what he used off the top of my head, but it looked nice on all of our laptops of varying sizes). This resolution did not hold up when we projected onto the screen in the room - this is something we will fix for the final presentation. We will definitely find a time to go in the room and test the HTML formatting within the room.

But the HTML format was not criticized as being poor in any regard, so kudos to Cameron for that. We inject records into the HTML as the driver runs and each record creates a new row in the HTML. At the time of our presentation, we were only saying which unit tests were running, a description of the test (the description included the method being tested and requirement), and a pass/fail slot. In order to make this more readable for anyone and everyone, we are having to change it up.

To change it up: Tyrieke started working on separating the method into its own "Method:" field in the HTML and putting the requirement in its own field. This is trivial as we are just manipulating a little bit of data that comes from the testCaseX.txt file. So we'll have the name of our input file we use for test cases and the name of the output and the name of the oracle. But here's an issue... we can't really show the inputs, expected output, and actual output on our html because Galaxy likes to use big files that have very unique formatting (fasta, for example).

So here's where I'm stepping in with my idea. After Tyrieke and Cameron finish their formatting, I had the idea of having the inputs, outputs, and oracles function as links to the files themselves. So we can click on (or maybe even hover over - get some CSS3 and HTML5 in the mix) the file and view the inputs, outputs, and oracles. This would make it so our HTML report meets all the requirements, all while I'm brushing up on some HTML5 (since I have not worked with it since early Summer.

Music listened to while blogging: N/A