Over the past week or so, I’ve been using this blog to capture my thoughts on my “What is Eclipse?” presentation. To recap, I start this conversation with an expectation that the listener is already familiar with Eclipse as a Java IDE (if they’re not then this is easy enough to cover).
My last few blog posts discuss a presentation that I regularly deliver titled “What is Eclipse?“. As previously discussed, I tend to introduce people to Eclipse by starting with what they already know: Eclipse is a movie about vampires that I have no intention of watching. Eclipse is a Java IDE.
A challenge that we revisit with some frequency is the Eclipse Elevator Pitch: How do you explain Eclipse in fifteen seconds? Ultimately, I’m not sure it’s possible. Pretty much every time I speak to a group, I spend time talking about Eclipse with a deck of slides that are aptly named “What is Eclipse?” [note-to-self: I need to update the uploaded version of these slides.].
I’ve been filling in some of the gaps in unit testing on the EclipseExamples project’s Eclipse Business Expense Reporting and Tracking (EBERT) component. My focus over the past several days has been to make sure that the user interface tests are as complete as I can make them. I thought I might spend a little time discussing some of the tests.