taylormck / graph Goto Github PK

Share the unit tests to the shared test repo

add_edge has an infinite loop or is ridiculously slow

has_cycle fails to find complex cycles, i.e., cycles that are more than one step.

There is no well defined end for the edge_iterators to compare to

After refactoring into a set of edges, the edge tests are failing. There must be a bug in the edge function.

Submit the project

Write unit tests before you write the code. When you encounter a bug, write a unit test that fails, fix the bug, and confirm that the unit test passes. Write at least an average of 3 unit tests for each function. Tests corner cases and failure cases. Name tests logically. Push and pull the unit tests to and from the grader's repository. Prepend - to the file names at GitHub (i.e. foo-TestGraph.c++ and foo-TestGraph.out). Reach consensus on the unit tests.
You must use Valgrind.

Test Groups

• Constructor / Assignment tests
• Implementation dependent function/method tests
• Interface tests with boost::adjacency_list

Come up with some preconditions and write a valid that asserts them.

Remember the google form

Use Doxygen to document the interfaces.
The above documentation only needs to be generated for Graph.h. Comment each function meaningfully. Use comments only if you need to explain the why of a particular implementation. Choose a coding convention and be consistent. Use good variable names. Write readable code with good indentation, blank lines, and blank spaces.

Use assert to check pre-conditions, post-conditions, argument validity, return-value validity, and invariants. Worry about this last, but your program should run as fast as possible and use as little memory as possible.

• Set up a private Git repository at GitHub, named cs378-graph
• Invite the grader to your repository

The vertex_iterator needs a push_back method so that we can push back to the corresponding lists

There is a compiler error in valid. Fix it.

Create an issue for each of the requirements in this table. Create an issue for each bug or feature, both open and closed. Describe, label, and prioritize each issue adequately. Create at least 10 more issues in addition to the requirements in this table.