This repository has been archived by the owner on Nov 19, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2k
Organize unit tests dependencies #24
Comments
This shouldn't be an issue anymore. |
Reopening this issue to track the following changes:
|
cesarsouza
added a commit
that referenced
this issue
Apr 14, 2015
cesarsouza
added a commit
that referenced
this issue
Apr 14, 2015
All unit test projects have been disentangled and now their references are restricted to same references that their target tested projects also have. A few implementations have been moved between projects, but compatibility should not have been broken. Some work also has been put in place to prepare for the AForge.NET merge. Merge branch 'GH-24' into development
|
cesarsouza
added a commit
that referenced
this issue
Apr 19, 2015
Is branch GH-24 active? Propose delete? |
No, it is not active, it can be deleted! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the main project, certain projects don't reference each other for obvious reasons. For example, Accord.Math cannot reference Accord.MachineLearning, but actually it is Accord.MachineLearning that should reference Accord.Math.
However, the same cannot be said for the unit tests. In the current version, the unit tests have references among themselves, which might be a bit confusing, specially if you are trying to disentangle them from the main project.
As such, uncommon dependencies must be removed, and the resulting broken tests and references should be fixed.
The text was updated successfully, but these errors were encountered: