You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't find a satisfying solution despite these discourses are pretty old. Even if the implementation is not going to be inside DataFrames.jl finally, I think it is a good place to start an issue here about it.
EDIT: Here an example for rich comparison, taken from the discourse thread.
I would summarize the missing feature as follows:
have a @test_compare_dataframes macro or similar which can truly deal with any kind of types (especially those who need isequal for comparison and those who need isapprox). It would be super helpful if such a test macro could have rich output explaining the mismatch in detail if a mismatch occured (similar to DeepDiffs)
also make the underlying method available outside the @test-framework for who knows what
The text was updated successfully, but these errors were encountered:
Then decide if it should be shipped with DataFrames.jl or some other package (e.g. it might turn out that proper styling would require extra dependencies, which we might want to avoid)
The case is for building tests around DataFrames.jl
(At least) two rather old discourse issue have been opened around this
I couldn't find a satisfying solution despite these discourses are pretty old. Even if the implementation is not going to be inside DataFrames.jl finally, I think it is a good place to start an issue here about it.
EDIT: Here an example for rich comparison, taken from the discourse thread.
I would summarize the missing feature as follows:
@test_compare_dataframes
macro or similar which can truly deal with any kind of types (especially those who needisequal
for comparison and those who needisapprox
). It would be super helpful if such a test macro could have rich output explaining the mismatch in detail if a mismatch occured (similar to DeepDiffs)@test
-framework for who knows whatThe text was updated successfully, but these errors were encountered: