Tag Archives: Automated Testing

Ubuntu Classroom: Ubuntu Developer Week: Review of Day 3

Unfortunately 13.04′s Ubuntu Developer Week is over. All the logs and videos are linked from the timetable, so you can still enjoy the sessions again and again. We hope you had a great time and we will see you soon again in one of our Ubuntu development channels.

Here’s what happened on day 3:

  1. Automated Testing in Ubuntu & Automated Testing TechnologiesMartin Pitt did a great job of summarising the current work in the Quality Assurance team. It’s getting more and more important to automatically assure us that software we rely on still provides the functionality we expect and nothing breaks. Check out the log and get an idea of how diverse the activities are and where you can get involved.
  2. Syncing your app’s data with u1dbStuart Langridge has been involved in Ubuntu One since ages and knows how to make app authors happy. If you want simple data storage and syncing without headaches, have a look at u1db and Stuart’s introduction to u1db!
  3. Interacting with Debian’s Bug Tracking System — You explain things best if you talk about things you make use of every day. As Stefano Rivera is both a Debian and Ubuntu developer, this talk was quite easy to deliver for him. Debian’s Bug Tracking System is a central place of exchange between the two projects and Stefano’s session will surely make it clearer to you.
  4. Building Ubuntu images & The Ubuntu Nexus 7 imagesOliver Grawert has been building Ubuntu images for various platforms for quite a few cycles already, so he knows the problems you probably run into most. His sessions give some good insight into what’s involved in bringing Ubuntu up on all kinds of devices.
  5. Fixing packages to cross-build — As a member of the Foundations team Dmitrijs Ledkovs has gathered quite some experience cleaning up problems, including build problems in the archive for a while now. Check out the session to find out how to make packages build for other architectures most easily. Get involved in fixing these issues once and for all.
  6. Developers RoundtableBenjamin Drung and Michael Bienia were kind enough to take on the last session of UDW and answer all the remaining questions regarding Ubuntu development. Be sure to check out the log as your favourite question might well be among the ones answered. :-)

Oh, and before we forget it: join us in the Automated Testing Hackfest today!


Source: FULL ARTICLE at Planet Ubuntu

Daniel Holbach: Automated Testing Hackfest

We all want more quality. We all wasted too many hours trying to fix broken software and we all know that new users struggle the most when facing crashes or other unexpected results. We probably all also agree that testing is a good idea and if it’s automated, then that’s even better.

Automatically exercising large parts of some software’s functionality helps a lot in guaranteeing that things still work, even if the code or some underlying foundations change. The idea is to write the test-case once and have it do its work whenever bits change and let us know if things break unexpectedly – especially before users run into bugs.

Tomorrow, 1st February 2013, we are going to hang out in #ubuntu-quality on irc.freenode.net to have a Hackfest about Automated Testing.

So what’s going to happen there?

  • We are going to have seasoned Ubuntu developers who will introduce you to autopilot (for UI testing) and autopkgtest (for integrating tests with the package in a more general sense).
  • We have a list of tests we want to work on together (but you can work on your own tests if you like as well).
  • We are going to have lots of fun and make Ubuntu a better place.

If you are interested, that’s great, because this is one of the coolest contributions to Ubuntu you can make. For autopkgtest it might be good to have at least a bit experience with scripting or programming, for autopilot less so. Be curious, be there, make Ubuntu better!

Check out our docs here and see you tomorrow!

 

Source: FULL ARTICLE at Planet Ubuntu

Daniel Holbach: Ubuntu Developer Week is back

The times for Ubuntu have never been more exciting. Cloud, server, desktop, laptop, TV, tablet, phone – everything runs Ubuntu or is soon going to. This makes developing Ubuntu very special, because fixes which go into Ubuntu in one place will benefit all form factors and all circumstances where it’s used. By improving Ubuntu you make millions of people around the globe happy.

During every 6 month release cycle we run Ubuntu Developer Week. It’s back and we’re going to have it from 29th January to 31st January. During the event we will have online sessions where seasoned Ubuntu developers introduce you to their respective area of expertise or to Ubuntu Development in general.

We will have many great sessions, from hands-on introduction to packaging and Ubuntu development to talks about how to quickly get involved in certain teams and interact with other projects. We will talk about tools and infrastructure, fixing bugs, finding memleaks, working with apps, create Ubuntu images and much much much more. This is the best opportunity to get a feel for how Ubuntu development works, get to know people and ask all the questions you might have.

I talked to a few session hosts, read below what they had to say.

Martin Pitt

Martin Pitt

Martin Pitt, who will talk about Automated Testing, says: “We have been, and are changing the Ubuntu development process to employ automated testing and avoid introducing regressions, and to improve confidence, focus, and development speed. In the first talk I will give an overview about the various kinds of tests that we do, so that you know where to watch out for failures and get debugging information. The second talk focuses on how to write tests, i.e. which technologies are available for e.g. hardware and GUI related behaviour or system-wide integration checks.”

 

Stefano Rivera

Stefano Rivera

Stefano Rivera, who will talk about Upstreams and Debian in particular, said: “So, working effectively in Ubuntu means also working with the teams and people upstream who wrote the software we distribute. I’ll talk about why this is important, when it’s necessary, and how to go about it. In particular, our most important upstream is Debian. Debian has a rather unusual (though powerful) bug-tracker. We’ll cover finding, submitting, and modifying bugs on it.

Chris Wilson

Chris Wilson

Chris Wilson, project leader of the Hundred Papercuts Team, says: “Unity may be the shiny new thing that everyone loves, but style without substance is only so much fluff, and the substance of Ubuntu is still its GTK-based apps. Once Hundred Paper Cuts focuses it’s attention on that substance, rubbing out the little annoyances that get under our skin every day we’re using Ubuntu. This session will introduce you to the project, how it works, and how to get involved. If you want to contribute to Ubuntu in a way that has the biggest impact on the quality of experience for the end user, then don’t miss this.

 

Bhavani Shankar

Bhavani Shankar

Bhavani Shankar, said about his talk about patch systems: “Many a time we wonder how to integrate a particular fix a particular part of the code in a program and upload into repositories without having to change code each time by hand and making it clumsy. In this session I’m going to show how to use different patch management systems that are in practice now.

About his talk about the app review process in Ubuntu he says: “In this session I’m going to explain the present workflow of reviewing apps and give an introduction into the new app dev upload process to automate reviews.

The forum we use for this is IRC, as it makes it easy to interact for many people without losing track, you can easily copy/paste and we can save the logs as searchable docs afterwards. You join in by simply connecting to #ubuntu-classroom on irc.freenode.net.

Check out the schedule and find more info on the Ubuntu wiki. We hope to see you all there, please let you friends know too. :-)

Source: FULL ARTICLE at Planet Ubuntu