HW25:Team Progress II
Team Progress II
The team has started significant work on the final paper and poster. We have a rough draft of each that will require some editing but by and large the bulk of the work is finished. That isn't to say there isn't work to do still. In the past week, we worked on polishing and commenting on the script to clarify how it operates and why it operates in a specific manner. The time I've been spending on bash has been surprisingly enjoyable. I enjoy its simplicity and its power at manipulating files and text. The script was also modified to compile all of the driver files at once to speed up the testing process. This may not be ideal if the user was going to create new test files as they would need to modify the current script to compile properly. Previously the script would handle any additional drivers but the way it was accomplishing this caused the script to run significantly longer.
Another thing that needed some work was the HTML document we have displaying the results of the test cases. Initially, I set out to fix the test case order in the HTML table. The script is built to read in every .txt file in a specified folder then parse the files and retrieve the test number, among other things, and that number is output to the HTML table. Because the files are sorted in the order, 1, 10, 11,...and therefore displayed oddly in the HTML table I sought to make the entire table sortable. This had the added benefit of being able to also sort the passed/failed column to bunch them altogether if desired. There was a simple, if not inefficient, sorting function at w3schools.com that required just a bit of modification to use in our table.
There were some things we overlooked that we are working to correct this week. We failed to put the requirements for the functions being tests in the table to add clarity to the results and inputs. This was something we had already identified as needing to be fixed but we overlooked it. Luckily it will only take a small modification to the script and test files to add that detail.
It's been a relatively productive 2 weeks.
The team has started significant work on the final paper and poster. We have a rough draft of each that will require some editing but by and large the bulk of the work is finished. That isn't to say there isn't work to do still. In the past week, we worked on polishing and commenting on the script to clarify how it operates and why it operates in a specific manner. The time I've been spending on bash has been surprisingly enjoyable. I enjoy its simplicity and its power at manipulating files and text. The script was also modified to compile all of the driver files at once to speed up the testing process. This may not be ideal if the user was going to create new test files as they would need to modify the current script to compile properly. Previously the script would handle any additional drivers but the way it was accomplishing this caused the script to run significantly longer.
Another thing that needed some work was the HTML document we have displaying the results of the test cases. Initially, I set out to fix the test case order in the HTML table. The script is built to read in every .txt file in a specified folder then parse the files and retrieve the test number, among other things, and that number is output to the HTML table. Because the files are sorted in the order, 1, 10, 11,...and therefore displayed oddly in the HTML table I sought to make the entire table sortable. This had the added benefit of being able to also sort the passed/failed column to bunch them altogether if desired. There was a simple, if not inefficient, sorting function at w3schools.com that required just a bit of modification to use in our table.
There were some things we overlooked that we are working to correct this week. We failed to put the requirements for the functions being tests in the table to add clarity to the results and inputs. This was something we had already identified as needing to be fixed but we overlooked it. Luckily it will only take a small modification to the script and test files to add that detail.
It's been a relatively productive 2 weeks.
Comments
Post a Comment