-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basic tests to catch edge cases #379
Conversation
(1) duplicate terms on the diagonal; and (2) duplicate terms on the off-diagonal, including duplicates of elements at locations (i,j) and (j,i).
Codecov Report
@@ Coverage Diff @@
## master #379 +/- ##
==========================================
+ Coverage 96.31% 96.35% +0.03%
==========================================
Files 40 40
Lines 4836 4884 +48
==========================================
+ Hits 4658 4706 +48
Misses 178 178
Continue to review full report at Codecov.
|
src/Test/UnitTests/constraints.jl
Outdated
MOI.set!(model, MOI.ObjectiveSense(), MOI.MaxSense) | ||
MOI.set!(model, | ||
MOI.ObjectiveFunction{MOI.ScalarAffineFunction{Float64}}(), | ||
MOI.ScalarAffineFunction{Float64}( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't have to explicitely specify the type {Float64}
. At least it is inconsistent with other tests
(1) duplicate terms on the diagonal; and
(2) duplicate terms on the off-diagonal, including duplicates of elements at locations (i,j) and (j,i).