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
{{ message }}
This repository was archived by the owner on Aug 2, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 2, 2020. It is now read-only.
Hi @snowleopard, @izgzhen,
Can you please give me an idea of more tests that we can perform.
Also, currently all tests are hardcoded, but I think we can introduce a bit of randomization to make the tests more effective.
Eg: The rule testModuleName currently has hardcoded ‘Data.Functor.Identity“. We can instead pick up any Module Randomly and test for that. @snowleopard
I'd say this whole issue is fairly low priority. It's great to have thorough tests to help maintain Hadrian in the long term, but we still have a lot of work before Hadrian becomes the default build system for GHC.
@snowleopard Giving it 3-4 days in my proposal. My proposal currently aims at making Hadrian more robust by implementing good test coverage, both from test suite as well as internally.
Activity
Add tests for matchVersionedFilePath.
Refactor Selftest, add more tests for matchVersionedFilePath.
Document and test encode/decodeModule.
Test findModuleFiles.
Add a selftest for Packages
Test conditions for building win32 and unix packages
chitrak7 commentedon Mar 22, 2018
Hi @snowleopard, @izgzhen,
Can you please give me an idea of more tests that we can perform.
Also, currently all tests are hardcoded, but I think we can introduce a bit of randomization to make the tests more effective.
snowleopard commentedon Mar 23, 2018
@chitrak7 We already use QuickCheck. What other randomisation do you have in mind?
chitrak7 commentedon Mar 25, 2018
Eg: The rule testModuleName currently has hardcoded ‘Data.Functor.Identity“. We can instead pick up any Module Randomly and test for that. @snowleopard
snowleopard commentedon Mar 25, 2018
Right, I see.
I'd say this whole issue is fairly low priority. It's great to have thorough tests to help maintain Hadrian in the long term, but we still have a lot of work before Hadrian becomes the default build system for GHC.
chitrak7 commentedon Mar 25, 2018
@snowleopard Giving it 3-4 days in my proposal. My proposal currently aims at making Hadrian more robust by implementing good test coverage, both from test suite as well as internally.