Die Blog-Einträge sind nur in englischer Sprache verfügbar.
Eclipse Testing Day 2013: Call for Papers and Sponsors
07.05.2013 11:45 von Alexandra Schladebeck
The theme for this year's Eclipse Testing Day is "mobile testing". The day will take place on 25th September in Darmstadt, and the call for papers and sponsors has started!
New challenges and experiences
The Eclipse Testing Day has been very successful over its past three years, and we intend to make the fourth year just as interesting for speakers, sponsors and attendees. We've chosen the exciting topic of mobile testing to reflect the new challenges is brings and the solutions it requires - be they technical, process-based or people-based.
The list of possible topics includes:
- Eclipse projects with mobile aspects - and their testing
- Cross-platform development and testing for mobile applications
- Eclipse tooling for developing and testing mobile applications
- UX design in mobile projects
- Case studies of mobile testing projects
- Mobile testing as a part of the application lifecycle
- Comparisons between testing in desktop and in mobile projects
- Manual, automated and crowd testing for mobile projects
- ... your own take on the topic of mobile testing
Submitting a paper is easy
Just send an email to firstname.lastname@example.org with your 150-word abstract (in English), a short biography and a picture by 21st June 2013.
Got a solution to share? Sponsor a great event
As in previous years, the Eclipse Testing Day is non-profit. Our sponsors and supporters are the backbone of the day. If your company is involved in mobile development or testing, then you should consider supporting a fantastic event while meeting interested participants. We've got various sponsor and mutual benefit packages available - and if you have a different idea for sponsorship, then we'd love to hear from you too!
An overview of the sponsor and support packages is on the Eclipse Wiki Sponsor page.
Here's to a successful testing event!
Eclipse Stammtisch in Braunschweig
17.04.2013 13:12 von Alexandra Schladebeck
Yesterday evening, we had the first Eclipse Stammtisch of 2013 here in Braunschweig. Since the topic in November (using e4 to write an application) was so well received, we stayed on the e4 track for this event. Sebastian Goebel presented the work they've been doing on migrating their application from an Eclipse 3-based framework to Eclipse 4. The "exotic" part - they are using Swing as a GUI toolkit.
One of the things that I love about the Eclipse community is when a talk includes the sentence "we saw this at a Demo Camp and decided to try it out". That's just what happened to Sebastian and his team - after seeing Kai Tödter's prototype for Swing renderers for e4, they realised that was just what they needed. After all, even though Swing is officially on its way out, their first consideration is to migrate their underlying platform. That way, they can gain the benefits of a more modern standard (that would be e4 ) without losing all of the work they've done on their GUI components - including custom controls and behaviour.
Sebastian gave a report of their progress up to now - after a three-week proof-of-concept phase, the decision was made that the move was feasible, and they're expecting the release to happen this summer. At a later point, they may move to JavaFX, but that's a different story.
Eclipse and Swing may seem like an unlikely pairing for some, but Sebastian's team have been using an Eclipse-based framework for years, and the work of people such as Kai Tödter and the Eclipse Scout team show that it's still of interest to the community. The most pleasing aspect for me though, was to hear that the prototype for Eclipse 4 + Swing was testable with Jubula / GUIdancer out-of-the-box, just like we found out for Scout applications .
New releases of GUIdancer and Jubula
18.03.2013 08:54 von Alexandra Schladebeck
Eclipse 4 support and iOS support in one release – it’s been an exciting time for the GUIdancer / Jubula team over the past few months!
Eclipse e4 support
From a development perspective, the Eclipse 4 support was very much an area that we are familiar with and posed almost no problems. The only challenge was pulling our internals apart and putting them back together to deal with differences between the 3.x and 4.x strands, but still profiting from the code reuse that was feasible for around 95% of our support.
The result is that, from a user perspective, almost nothing has changed. We put a lot of thought into the packaging of our support plugins (the RCP accessor), and decided that we wanted Jubula or GUIdancer to be able to decide which plugins need to be started. So, in this version, as in the previous versions, there is still one zip file whose contents have to be added to the plugins folder of your AUT, and the rest is done for you. It was certainly exciting to see the first tests running on pure e4 applications (we’re writing one for a customer, so we had a chance to eat our own dogfood fairly early on), and the support for e4 with compat layer means we can also finally consider moving to Juno or Kepler – we could test ourselves now.
On a wholly different (but equally exciting) topic, we’ve also made our first step into the test automation for the mobile world. The iOS support is only in GUIdancer, but we encourage everyone to get a demo license and try it out for 30 days to see what you think.
Again, we put a great deal of work into making sure that as many concepts remain the same for testing iOS applications as they are for desktop toolkits. Most of the actions already available for the desktop components can be used for iOS as well. So you can use the unbound modules to click (tap), to execute actions on lists, tabbed components, combo components etc.
Nevertheless, there are some technically motivated differences that are worth mentioning briefly (more information is in the documentation, and we’re planning some more blogs with examples):
- Adapting the AUT : it’s a technical necessity to make an iOS AUT accessible for testing. The work to do isn’t much – just adding some header files to a test version of your app, and maybe adding some component naming if you want to show your love for your testers (which we assume you do :) )
- Starting the AUT : for iOS applications, the AUT already has to be started, either on the device or on the simulator, in order to test it. The „Start AUT“ function from the ITE or from the testexec just connects to the AUT. The basic gist of these two points is that the development team should ensure that the AUT is testable and deployed for the tester.
- Object mapping: You can generally collect and address a great deal more components in an iOS app than in a desktop app (for example, a button with a label can be broken into its composite components of button and label). The same applies to complex controls such as Table Views, which can be addressed as lists, or as any of the components they contain. There is more of a decision-making process involved in choosing the correct component to test, and this is reflected in the object mapping. We’ve implemented three gestures for object mapping:
- A single tap collects the component you tap.
- A double tap collects the component you tap and its parent. This is particularly useful for collecting the button "behind" its label, for example.
- A long tap of more than two seconds collects all currently visible components.
So some parts have changed, but the general concepts and principles have remained the same. As with e4 support, we’ve also been testing this on a customer application, and we’re excited about getting feedback from our users.
There are some other goodies in both tools too. Dedicated 32- and 64-bit installers, screenshots for errors in HTML reports, Windows 8 support, and a much more compact properties view. We’ve also made navigation easier – double-clicking items in browsers will now open the parent Test Case for that item. Double-clicking in editors now opens the item you double-clicked. These are suggestions that have come in from you, our users, and we’re happy with the effects – it’s much easier to work with the tool.
In just a couple of days, we’ll be heading to EclipseCon in Boston. Come and chat to us to ask us about the new version, participating on the project, and your own testing projects.
Agile Dev Practices round-up
06.03.2013 11:05 von Alexandra Schladebeck
This year was the first year of the Agile Dev Practices conference in Potsdam, and although I could only make it for one day, I took a great deal back from the talks and the people I met.
Keynote - Practices and Principles
The format of the keynote was great - using cartoon potatoes to represent members of the agile team. Andrea made some good points about what following a practice without understanding the principle behind it can do. If stand up meetings feel like control meetings, planning meetings feel like being shot at with stories, and retrospectives feel like you have to defend yourself, then something is very wrong. I liked his point about agile being about capacity management - you can't make (some old type of) printer print more than 6 pages a minute, and any attempt to do so will result in a paper jam. He talked about the team pulling from the backlog instead of having things pushed on them, and I liked that too. I'd argue that teams starting out with agile will usually (have to) begin with the practices. They should review them frequently ensure they are really in line with the principles (kind of like introducing agile iteratively) - but his warning signs are valid for all teams, regardless how long they've been together.
Agile Test Automation at Xing
This talk was an overview of how teams work at Xing, with a focus on the test automation for the mobile applications. It is fascinating to me that there are separate teams to work on separate applications - it clashes with the "write once, run anywhere" principle that we know from the desktop - and that I know BREDEX has as its aim for mobile development and test automation as well. Unfortunately I didn't get to chat to Sergej for very long because of the next talk, but he did make the point about different user circles and their expectations from an app. I'll be interested to hear from other mobile talks how other teams deal with cross-platform development and testing.
Exploratory testing for developer, testers and you
I was undecided about whether to attend this talk, because I've heard various talks on exploratory testing. I enjoy them, but I was unsure about whether I'd learn something new. I was so glad I went! I liked the very logical explanation of automating what we know to make sure we always know it, and using exploratory testing to find out what we don't know we don't know (second order ignorance). The real benefit from this session for me was session-based test management (SBTM). I'd heard about it before, but had never really been able to understand how to put it into practice. As luck would have it, our team had made the decision to have a "Test Day" just last week, and suddenly SBTM fell into place for me. Meike, Markus and Sven from Atlassian gave me some excellent tips after the talk, and we're going to try it out next Monday for our Test Day.
Dialogue Sheets for retrospection
This was a workshop using Allan Kelly's dialogue sheets to guide teams through a retrospection. I enjoyed the sheets - and the most useful part for me was chatting to the others in the team about our problems. I shared some of our current problems and got some good tips, and was able to share some solutions we've tried. A good session.
Aiming Higher - using test automation to drive better quality
This was the talk I held. As a non-developer, I was a little nervous about speaking to a room of developers - especially on a topic that can be translated as "how to take little steps to get benefits and use them as leverage to get the team to do more for CI and continuous testing". As it turned out though, I had a good mix of roles, and even the developers listened with open ears
Seriously though, the talk was about taking a very agile approach to test automation. Every little step already brings benefits - even if the whole aim isn't achieved. Sometimes the person or people driving the test automation need leverage to get the tools (in an abstract sense) they need, and I hope the talk provided some nuggets of information to take home.
Home was the operative word after the talk - I had to leave before the last keynote. But, the day was well worth it, and I'm looking forward to putting the things I learned into practice.
Meet us at EclipseCon in March!
21.02.2013 09:26 von Alexandra Schladebeck
EclipseCon is only a few weeks away, and we are particularly excited about it this year. As well as giving three talks over the course of the week , we can’t wait to get the first feedback about the new versions of GUIdancer and Jubula. They’ll be released on 19th March and contain two very exciting features, which we’re sure you’ll love: e4 support and iOS support.
Admittedly, we’re not as quick off the mark on this one as we’d have liked to have been, but nevertheless we’re proud to be able to release the support in the Jubula standalone as a preview for Kepler. We’ve already tested a customer project with the latest version, and can’t wait to offer it to the community.
GUIdancer customers will get the extra benefit of our new support for iOS applications. The concepts for test automation that you know and love from Swing, SWT/RCP/GEF, HTML and .NET have been transferred to the mobile world, and we’re looking forward to making it available. We’ve also been using this new toolkit in our projects – it’s a relief to finally be able to reap the benefits of automated testing in mobile applications as well.
Three team members from Jubula / GUIdancer will be at EclipseCon, and we’ll be very happy to meet anyone interested in the work we’ve been doing, as well as any testers working with the tools or wanting to find out more. See you in Boston!