itwinjs-core icon indicating copy to clipboard operation
itwinjs-core copied to clipboard

Introduce vitest to core/quantity

Open anmolshres98 opened this issue 1 year ago • 7 comments

Continuation of this effort: #7165

anmolshres98 avatar Oct 19 '24 14:10 anmolshres98

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 19 '24 14:10 mergify[bot]

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 20 '24 05:10 mergify[bot]

can you edit the launch.json debug profile for running core quantity tests to be the same as core bentley and common

hl662 avatar Oct 21 '24 19:10 hl662

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 22 '24 05:10 mergify[bot]

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 23 '24 05:10 mergify[bot]

can you edit the launch.json debug profile for running core quantity tests to be the same as core bentley and common

done

anmolshres98 avatar Oct 23 '24 05:10 anmolshres98

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 23 '24 20:10 mergify[bot]

My only feedback is that in some places you go from assert.strictEqual to vitest's toEqual, when technically they are slightly different including that strictEqual asserts the types are identical and toEqual doesn't (toStrictEqual would be the equivalent). If the tests pass I don't think this is worth changing though

eringram avatar Oct 24 '24 17:10 eringram

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Oct 30 '24 05:10 mergify[bot]

This pull request is now in conflicts. Could you fix it @anmolshres98? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

mergify[bot] avatar Nov 09 '24 05:11 mergify[bot]