Repository navigation
Testing
Testing was very important during the development process, initially our testing for our basic implementation consisted of the following:
- NodesTest
- EdgesTest
- IntegrationTest
- ProcessorTest
- SchedulerTest
- IOTest
As our implementation for our final implementation changed drastically from the basic implementation, this meant the tests also had to change alongside this.
The first tests that were changed were the Nodes and Edge test classes. Since we moved from having Node,Edge objects into int[][] arrays which stored node,edges, it meant that these tests had to change too.
The tests we ended up with were :
- OptimalityTest
- CommandLineParserTest
- InputFileReaderTest
Tests for correct optimality (finishing time) of different structured graphs, ensuring that our implementation of the algorithm produced the correct optimal finishing time for EVERY type of graph.
Tests that ensured any correct/incorrect command line inputs were dealt with accordingly.
Tests that the weights of nodes added is correct, that the input file being parsed in, is being parsed correctly into our data structures.
- Home
- Team Details
- Meeting Minutes
- Project Resources & Specifications
- Conventions
- Basic Implementation
- Optimal Implementation
- Algorithm Optimisations