Fast unit tests for Eclipse Plugins
2 likes624 views
The document discusses the possibilities and tooling for fast unit testing of Eclipse plugins, emphasizing the importance of achieving quick feedback within the IDE. It outlines various architectural approaches for testing, including different dependencies and plugin configurations, while stressing clean runtime conditions and efficiency. Additionally, it hints at the need for continued improvements in testing practices and tools within the Eclipse ecosystem.
Fast unit tests for Eclipse Plugins
- 1. FAST UNITS TESTS FOR ECLIPSE PLUGINS Possible architectures and available tooling Aurélien Pupier Senior Software Engineer 9th June 2016 @apupier
- 2. 2 / 26 What happened? ●http://www.commitstrip.com/en/2016/03/15/how-to-optimise-your-time-as-a-coder/
- 3. 3 / 26 Response Time Limits 0 5 10 15 20 25 30 35 s JUnit Plugin with Workbench JUnit Plugin Headless JUnit user's flow of thought broken 1 Sec lost the user's attention 10 Sec
- 4. 4 / 26 Objective Stay Focused
- 5. 5 / 26 In our case... Fast feedback from (unit) tests in IDE
- 6. 6 / 26 Time to launch Tests 0 5 10 15 20 25 30 35 s JUnit Plugin with Workbench JUnit Plugin Headless JUnit
- 7. 7 / 26 Plain JUnit Tests for plugins Several possibilities No consensus
- 8. 8 / 26 Architecture possibilities src src/test/java src src/test/java src/test/javasrc src src/test/java
- 9. 9 / 26 User Library inside plugin src
- 10. 11 / 26 User Library inside plugin src src/test/java
- 11. 12 / 26 User Library inside plugin ● Clean Runtime ● Small tests ● Build time ● Fragment test ● No third-party: – – – Your test toolkit
- 12. 13 / 26 Optional dependency inside plugin src
- 13. 14 / 26 Optional dependency inside plugin src src/test/java
- 14. 15 / 26 Optional dependency inside plugin ● Third-parties: – – – Your test toolkit ● RCP application not planned to be extended by third-parties ● Pollute runtime!
- 17. 18 / 26 Fragment ● Clean runtime ● Third-parties: – – – Your test toolkit ● Most powerful with clean runtime ● > Built-time ● Repository Complexity ● Test fragments
- 18. 19 / 26 Test plugin src
- 19. 20 / 26 Test plugin src src/test/java
- 20. 21 / 26 Test plugin ● Third-parties: – – – Your test toolkit ● Single plugin for integration tests ● Pollute runtime! ● > Built-time ● Repository Complexity ● Package scoped
- 21. 22 / 26 Architecture possibilities src src/test/java src src/test/java src/test/javasrc src src/test/java
- 22. 23 / 26 All tests are important! We talked here
- 23. 25 / 26 Tooling demo https://github.com/apupier/EclipsePlugins- Testing
- 24. 26 / 26 Going further ● Test classpath supported by PDE and Tycho? ● Pre-mocked E4 Context? ● MoreUnit automatic configuration support? ● Fast Integration/UI tests continuous feedback?
- 26. 28 / 26 References ● https://rcpquickstart.wordpress.com/2007/06/20/unit- testing-plug-ins-with-fragments/ ● https://resheim.net/2014/12/unit-testing-eclipse-rcp- applications.html ● https://www.nngroup.com/articles/response-times-3- important-limits/ ● http://www.commitstrip.com/en/2016/03/15/how-to- optimise-your-time-as-a-coder/