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 "Eclipse Testing Day 2012 Talks"
(New page: = Talks<br> = == Testing of Eclipse RCP based Products<br> == Stability is a key requirement for an established product. Of course, software is never bug free, but bugs being fixed must ...) |
|||
| Line 1: | Line 1: | ||
| − | = Talks<br> = | + | = Talks<br> = |
| − | == Testing of Eclipse RCP based Products<br> == | + | == Testing of Eclipse RCP based Products<br> == |
| − | Stability is a key requirement for an established product. Of course, software is never bug free, but bugs being fixed must stay so in later releases. As manual testing is error prone and quite expensive, consequent automated testing is the logical implication. | + | Stability is a key requirement for an established product. Of course, software is never bug free, but bugs being fixed must stay so in later releases. As manual testing is error prone and quite expensive, consequent automated testing is the logical implication. |
| − | Especially in the case of Eclipse RCP applications and Plug-Ins, being delivered to different target platforms and installed into many possible client configurations, migration and system testing is also important. | + | Especially in the case of Eclipse RCP applications and Plug-Ins, being delivered to different target platforms and installed into many possible client configurations, migration and system testing is also important. |
| − | So we're facing challenges on multiple very different layers. In the talk we present our approach to clearing the fog starting with unit testing to black-box UI tests - and talk about our DOs and DON'Ts of using technologies from Jenkins to Jubula. <br> | + | So we're facing challenges on multiple very different layers. In the talk we present our approach to clearing the fog starting with unit testing to black-box UI tests - and talk about our DOs and DON'Ts of using technologies from Jenkins to Jubula. <br> |
| − | '''Manuel Bork, Yatta Solutions GmbH'''<br> | + | '''Manuel Bork, Yatta Solutions GmbH'''<br> |
| − | Manuel Bork is a passionate software developer, committed IT consultant and dedicated Eclipse enthusiast. At Yatta Solutions Manuel works on UML Lab's Round-Trip-Engineering technology. He is Eclipse committer for the Eclipse MFT project, and he loves mountain biking in his free time.<br> | + | Manuel Bork is a passionate software developer, committed IT consultant and dedicated Eclipse enthusiast. At Yatta Solutions Manuel works on UML Lab's Round-Trip-Engineering technology. He is Eclipse committer for the Eclipse MFT project, and he loves mountain biking in his free time.<br>Email: bork@yatta.de, Twitter: @manuelbork. Web: http://www.yatta.de <br> |
| − | + | <br> | |
| − | <br> | + | == Cutting the right corners: Achieving the balance between effort and payoff for GUI test automation<br> == |
| − | + | If budgets, resources and time are tight, then one of the first things to suffer is testing. While it’s only natural (and perfectly correct) to want to minimize any waste, it’s important not to cut corners in the wrong place. <br> | |
| − | + | This talk looks at the case study of a project that began in a fixed-price phase, with automated GUI tests running in parallel with development. The quality of the released software convinced the team and customer that test automation was a good investment. However, due to personnel and project constraints, it was not possible to have a dedicated tester for the project after the fixed-price phase. <br>Through various iterations, the team was able to find a good balance between effort and payoff with GUI test automation. They were able to identify factors that can be reduced without negative consequences (constant tester presence in the project, for example) as well as aspects that are mandatory for success (continuous build, regular test analysis and maintenance, good test design). As well as technical requirements for good-value test automation, they were able to identify ways to find and train good testers. <br>This talk presents the journey of the project and their ways to achieve good results with minimal effort. <br> | |
| − | + | '''Alexandra Schladebeck, BREDEX GmbH'''<br> | |
| − | + | Alexandra earned a degree and an MA in linguistics from York University before starting work at BREDEX GmbH, where she is a trainer and consultant for automated testing and test processes. As product owner for the Eclipse Jubula Project, and its “big brother” GUIdancer, she is responsible for developing user stories with customers as well as documentation and testing. Alex frequently represents BREDEX at conferences, where she talks about agility and testing from project experience. She is also involved in event organisation and customer communication. | |
| − | + | <br> | |
| − | + | == Java Development with Contracts in Eclipse<br> == | |
| − | + | In our talk, we would like to introduce the concept and tool support for Java development with Contracts in Eclipse.. | |
| − | + | Design by Contract (DbC) is a long forgotten methodology, allowing the specification of software by formulating pre- and post-conditions explicitly in the code. But with increasing complexity of modern software, it was rediscovered and is becoming more popular, for example with Code Contract for .NET. | |
| + | |||
| + | In order to provide similar functionality for Java, we have developed a Contracts framework for Java, named C4J. It can easily be integrated in new and existing Eclipse projects. Compared to similar approaches, it has the advantage of being 'refactoring-safe': the Contract code won't become invalid after automated refactorings in the IDE. On top of that, we’d like to share our progress in developing an accompanying Eclipse plugin, providing similar functionality for C4J as Eclipse and MoreUnit already do for JUnit. | ||
<br> | <br> | ||
| + | |||
| + | '''Stefan Schürle'''<br>Stefan Schürle is software developer with a main focus on developing RCP Applications with agile methods like TDD and SCRUM. | ||
| + | |||
| + | '''Ben Romberg'''<br>Ben Romberg is software developer at andrena objects and the developer of C4J 4.0. His main interests are automated tests and contracts for Java. <br> | ||
| + | |||
| + | == Iterative Model Based Generation of Test Cases for Graphical User Interfaces<br> == | ||
| + | |||
| + | Using activity diagrams as a means to generate and understand Test Cases has various advantages. Activity diagrams are reasonably easy to create and understand, and can offer a more clear view of a Test Case in a graphical form.<br>Nevertheless, using activity diagrams for Test Case generation does involve some tricky aspects such as keeping the diagram and the Test Cases in sync. In this presentation, we show how Test Cases can be automatically generated from activity diagrams and vice-versa. We discuss the practical uses as well as the limitations of the technique.<br> | ||
| + | |||
| + | '''Raimar Buhmann'''<br> | ||
| + | |||
| + | Raimar received his BSc in Computer Science in 2010 from the Technical University of Braunschweig. He is currently studying for his Master’s degree in Computer Science and writing his MSc Thesis on computer science on “Model Based Testing of Applications with Graphical User Interfaces“ in cooperation with BREDEX GmbH.<br> | ||
| + | |||
| + | '''Johannes Bürdek'''<br> | ||
| + | |||
| + | Johannes Bürdek is an employee at BREDEX GmbH and Master’s student in Computer Science at the Technical University in Braunschweig. The topic for his Master’s thesis is the generation of activity diagrams from test cases for graphical user interfaces.<br> | ||
| + | |||
| + | <br><br> | ||
| + | |||
| + | <br> | ||
<br> | <br> | ||
Revision as of 02:51, 4 July 2012
Contents
Talks
Testing of Eclipse RCP based Products
Stability is a key requirement for an established product. Of course, software is never bug free, but bugs being fixed must stay so in later releases. As manual testing is error prone and quite expensive, consequent automated testing is the logical implication.
Especially in the case of Eclipse RCP applications and Plug-Ins, being delivered to different target platforms and installed into many possible client configurations, migration and system testing is also important.
So we're facing challenges on multiple very different layers. In the talk we present our approach to clearing the fog starting with unit testing to black-box UI tests - and talk about our DOs and DON'Ts of using technologies from Jenkins to Jubula.
Manuel Bork, Yatta Solutions GmbH
Manuel Bork is a passionate software developer, committed IT consultant and dedicated Eclipse enthusiast. At Yatta Solutions Manuel works on UML Lab's Round-Trip-Engineering technology. He is Eclipse committer for the Eclipse MFT project, and he loves mountain biking in his free time.
Email: bork@yatta.de, Twitter: @manuelbork. Web: http://www.yatta.de
Cutting the right corners: Achieving the balance between effort and payoff for GUI test automation
If budgets, resources and time are tight, then one of the first things to suffer is testing. While it’s only natural (and perfectly correct) to want to minimize any waste, it’s important not to cut corners in the wrong place.
This talk looks at the case study of a project that began in a fixed-price phase, with automated GUI tests running in parallel with development. The quality of the released software convinced the team and customer that test automation was a good investment. However, due to personnel and project constraints, it was not possible to have a dedicated tester for the project after the fixed-price phase.
Through various iterations, the team was able to find a good balance between effort and payoff with GUI test automation. They were able to identify factors that can be reduced without negative consequences (constant tester presence in the project, for example) as well as aspects that are mandatory for success (continuous build, regular test analysis and maintenance, good test design). As well as technical requirements for good-value test automation, they were able to identify ways to find and train good testers.
This talk presents the journey of the project and their ways to achieve good results with minimal effort.
Alexandra Schladebeck, BREDEX GmbH
Alexandra earned a degree and an MA in linguistics from York University before starting work at BREDEX GmbH, where she is a trainer and consultant for automated testing and test processes. As product owner for the Eclipse Jubula Project, and its “big brother” GUIdancer, she is responsible for developing user stories with customers as well as documentation and testing. Alex frequently represents BREDEX at conferences, where she talks about agility and testing from project experience. She is also involved in event organisation and customer communication.
Java Development with Contracts in Eclipse
In our talk, we would like to introduce the concept and tool support for Java development with Contracts in Eclipse..
Design by Contract (DbC) is a long forgotten methodology, allowing the specification of software by formulating pre- and post-conditions explicitly in the code. But with increasing complexity of modern software, it was rediscovered and is becoming more popular, for example with Code Contract for .NET.
In order to provide similar functionality for Java, we have developed a Contracts framework for Java, named C4J. It can easily be integrated in new and existing Eclipse projects. Compared to similar approaches, it has the advantage of being 'refactoring-safe': the Contract code won't become invalid after automated refactorings in the IDE. On top of that, we’d like to share our progress in developing an accompanying Eclipse plugin, providing similar functionality for C4J as Eclipse and MoreUnit already do for JUnit.
Stefan Schürle
Stefan Schürle is software developer with a main focus on developing RCP Applications with agile methods like TDD and SCRUM.
Ben Romberg
Ben Romberg is software developer at andrena objects and the developer of C4J 4.0. His main interests are automated tests and contracts for Java.
Iterative Model Based Generation of Test Cases for Graphical User Interfaces
Using activity diagrams as a means to generate and understand Test Cases has various advantages. Activity diagrams are reasonably easy to create and understand, and can offer a more clear view of a Test Case in a graphical form.
Nevertheless, using activity diagrams for Test Case generation does involve some tricky aspects such as keeping the diagram and the Test Cases in sync. In this presentation, we show how Test Cases can be automatically generated from activity diagrams and vice-versa. We discuss the practical uses as well as the limitations of the technique.
Raimar Buhmann
Raimar received his BSc in Computer Science in 2010 from the Technical University of Braunschweig. He is currently studying for his Master’s degree in Computer Science and writing his MSc Thesis on computer science on “Model Based Testing of Applications with Graphical User Interfaces“ in cooperation with BREDEX GmbH.
Johannes Bürdek
Johannes Bürdek is an employee at BREDEX GmbH and Master’s student in Computer Science at the Technical University in Braunschweig. The topic for his Master’s thesis is the generation of activity diagrams from test cases for graphical user interfaces.