jpasski
commented
6 years ago JavaExec seems to be the way to go. However, Burp would need to terminate gracefully on its own. This could be performed via an extension that, once loaded, calls whatever it needs to do and then calls burp.IBurpExtenderCallbacks.exitSuite(boolean). It also should start burp in headless mode (-Djava.awt.headless=true). This forum post alludes to the extension needing to be loaded first and then its configuration stored.
- Obtain free burp
- Create a simple integration test extension that calls whatever tests are needed. Whatever is being tested also needs to be verified in the extension, not in some extra JUnit test. A failure needs to return a non-zero status.
- Load this extension (should be available on the classpath) into burp, either via the UI and store/reload configs or via classpath directly. TBD.
- Execute burp in headless mode via a gradle task.
- Make the itest task dependent upon this gradle task.
- Set a watchdog timer in the extension to kill it after some amount of time, returning a non-zero value if it fires.
- Otherwise, exit the suite w/o prompting the user. This should return zero.
Create an integration test that starts the free version of Burp and verifies a request is sent to a mocked proxy when extension is loaded and mocked proxy is configured. Bonus points for negative tests if possible.