Difference between revisions of "Team:Michigan Software/Proof"
| Line 48: | Line 48: | ||
<div> | <div> | ||
<h3>Unit Testing</h3> | <h3>Unit Testing</h3> | ||
| − | <p>We used the built-in unittest module to verify the functionality of our software, as is recommended in the Django documentation. In particular, we ran tests on <em>THESE | + | <p>We used the built-in unittest module to verify the functionality of our software, as is recommended in the Django documentation. In particular, we ran tests on <em>THESE THINGS</em>. Our software passed these preliminary tests, and so we took to user testing to continue with the verification.</p> |
<h3>User Testing</h3> | <h3>User Testing</h3> | ||
<p>Once ProtoCat 3.0 went live, we began by testing the interface . and then let other people use it. Including but not limited to Michigan iGEM team, Rice University iGEM team, and Josh's co-workers in lab. </p> | <p>Once ProtoCat 3.0 went live, we began by testing the interface . and then let other people use it. Including but not limited to Michigan iGEM team, Rice University iGEM team, and Josh's co-workers in lab. </p> | ||
Revision as of 00:14, 19 October 2016
Michigan Software Team
Protocat 3.0 - Proof of Concept
Unit Testing
We used the built-in unittest module to verify the functionality of our software, as is recommended in the Django documentation. In particular, we ran tests on THESE THINGS. Our software passed these preliminary tests, and so we took to user testing to continue with the verification.
User Testing
Once ProtoCat 3.0 went live, we began by testing the interface . and then let other people use it. Including but not limited to Michigan iGEM team, Rice University iGEM team, and Josh's co-workers in lab.
