i had this yesterday 🙂 if you click the magnifying glass on the result, and use the right-most scrollbar you should be able to check what assertions were run.
i think it's related to using both scenarios and defaultTest -- i restructured my tests after that and i'm back to a single assertion.
n
nyellin.
06/22/2024, 6:40 PM
I see the same assertion running twice
nyellin.
06/22/2024, 6:40 PM
Yep, I think its a bug with scenarios
nyellin.
06/22/2024, 6:40 PM
@ian would it be useful to open a github issue for this?
s
ssmith4498
06/22/2024, 6:44 PM
in my restructure, i'm still using scenarios but removed the defaultTest and i'm not getting the double assertions.
n
nyellin.
06/22/2024, 7:35 PM
Ah, that could work for me
s
ssmith4498
06/23/2024, 7:41 AM
yes -- honestly, i've found that having simpler basic configs, a few folders and running different evals from the command line is working better for me than bigger combined fixtures so far (and it's easy enough to put specific cases in shell scripts).