The tests run a Debuggee, make requests and call GHC.Debug.Client functions. To guard the tests against GHC changes, they make very little assumptions.
I'd like to propose this nomenclature for tests in this project:
system test - The library is used to inspect a real executeable (that runs).
functional test - Communication is done via socket, but there is some mock that answers.
unit test - Testing pure code.
This PR implements system tests. They make sure that Debugger and Debuggee can talk to each other.
Refers to #2
(Sorry, I had to close the previous PR because I mixed up GitLab WIP branches with GitHub Draft PRs.)
The tests run a
Debuggee, make requests and callGHC.Debug.Clientfunctions. To guard the tests against GHC changes, they make very little assumptions.I'd like to propose this nomenclature for tests in this project:
This PR implements system tests. They make sure that
DebuggerandDebuggeecan talk to each other.Refers to #2
(Sorry, I had to close the previous PR because I mixed up GitLab WIP branches with GitHub Draft PRs.)