{"action":"opened","issue":{"url":"https://api.github.com/repos/rocky/emacs-dbgr/issues/68","labels_url":"https://api.github.com/repos/rocky/emacs-dbgr/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/rocky/emacs-dbgr/issues/68/comments","events_url":"https://api.github.com/repos/rocky/emacs-dbgr/issues/68/events","html_url":"https://github.com/rocky/emacs-dbgr/issues/68","id":122285664,"number":68,"title":"Howto make test-simple invoke a real debugger","user":{"login":"cohomology","id":1144278,"avatar_url":"https://avatars.githubusercontent.com/u/1144278?v=3","gravatar_id":"","url":"https://api.github.com/users/cohomology","html_url":"https://github.com/cohomology","followers_url":"https://api.github.com/users/cohomology/followers","following_url":"https://api.github.com/users/cohomology/following{/other_user}","gists_url":"https://api.github.com/users/cohomology/gists{/gist_id}","starred_url":"https://api.github.com/users/cohomology/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cohomology/subscriptions","organizations_url":"https://api.github.com/users/cohomology/orgs","repos_url":"https://api.github.com/users/cohomology/repos","events_url":"https://api.github.com/users/cohomology/events{/privacy}","received_events_url":"https://api.github.com/users/cohomology/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-15T14:36:38Z","updated_at":"2015-12-15T14:36:38Z","closed_at":null,"body":"In my struggle to fix #65 and to understand realgud a bit more, I found some more bugs. Thus before fixing them, I wanted to write a test to reproduce them. As the test folder currently contains only unit tests, I thought I could add some tests which invoke a real debugger (gdb, say) and execute a few realgud commands (aka integration tests). See my [branch](https://github.com/cohomology/emacs-dbgr/commit/a7b1979edcededbf833d6cfc61924482fbc7cf33) for my progress in my branch feature/test_gdb.\r\n\r\nSo I added a configure options to detect whether gdb is installed and new test targets.\r\n\r\nWhen running my gdb-test-invoke.el test, I always get the message\r\n\r\n    I don't have /usr/bin/gdb listed as a debugger.\r\n \r\nI don't have figured out yet what the problem actually is, but my question would be how a correct approach in building integration tests would look like, before I run in the totally wrong direction."}}