xfail for test_G_star_Row_Standardized

[jGaboardi]

This PR resolves #331

[martinfleis]

Why do you do this?

[jGaboardi]

As a fail safe so it fails exactly when no warnings are emitted. I could not figure out how to add that granularity to parametrize_w without it affecting other tests. Maybe I'm missing something easy? Any thoughts?

I couldn't determine the proper raises argument for pytest.mark.xfail and I think having only a general failure is too vague.

[martinfleis]

But this makes no difference, no? You are just doing explicitly what pytest would do here anyway. I probably don't follow here...

We can also split this into two tests, one checking the warning and the other the values.

[jGaboardi]

I probably don't follow here...

I didn't explain well. What I mean it that I could not find the proper pytest error type to include in the xfail(raise=) parameter - the error raised when no warnings are emitted when in pytest.warns context.

We can also split this into two tests, one checking the warning and the other the values.

This may be the way to go if there isn't a more elegant solution that I am overlooking.

[martinfleis]

I'd probably split it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.3%. Comparing base (c6ca25f) to head (91df530).
Report is 2 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #336   +/-   ##
=====================================
  Coverage   81.3%   81.3%           
=====================================
  Files         24      24           
  Lines       3333    3331    -2     
=====================================
  Hits        2709    2709           
+ Misses       624     622    -2     

see 1 file with indirect coverage changes