Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseTestingDay2010 Talk Bredex"
(New page: == Automated acceptance testing for Eclipse applications – why, what and how? == The importance of acceptance testing tends to be underestimated. Often, very little in the way of testi...) |
(No difference)
|
Revision as of 08:52, 22 July 2010
Automated acceptance testing for Eclipse applications – why, what and how?
The importance of acceptance testing tends to be underestimated. Often, very little in the way of testing is done between the JUnit tests at the beginning of development and the rushed manual test at the end. But acceptance tests tell us whether or not the software being developed is actually doing what the customer ordered and give us a great opportunity to amend misunderstandings and problems before a product is even released.
This talk looks at why acceptance testing is so important and examines different ways of performing acceptance testing, with their advantages and disadvantages. We offer some practical tips on introducing and improving acceptance testing for Eclipse applications, including considerations about process and team, methodologies, frameworks and tools. Along the way, we use Eclipse applications to give examples of acceptance tests that will improve the outcome and quality of the development process.