Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
welcome so it's a little bit after 215 so we're going to go ahead and get started with the presentation today which will follow pretty closely the outline that we had on the program which is about assuring quality on drupal.org so it'd be a little
bit of history about testing i'm going to talk for I hope not more than 10 minutes and then we're going to split into a couple of groups and so I'll tell you about that most of this should be conversation on some very specific topics so to get
started what we did way back when is worked on be had tests for drupal org and so this is just if you've never seen what B hat does it allows you to describe functionality in relatively stylized but plain language that project managers and product owners
can read and then turn them into executable tests either using a browser or using a headless browser so that's the basic concept and the reason that we started this project at all is that Sam and Howard and I along with a lot of other people worked on
the get migration and a big part of what we spent hours and hours doing was making sure every time we integrated code that things were still working and we did all of that manually and it was pretty much me and Sam and then opening it up to other people to
repeat the work that we've done and neither of us ever wanted to do that again in our lives so this was something to learn to allow us to focus on other functionality so this testing project had a fairly long history and we've had a lot of people who've
been really supportive of the process we started it off long after the get migration in April of 2012 as a volunteer project with just some of us from the get team who wanted to do the testing it we actually received the donation of six months of developer
time from capgemini for three developers they were available to the community to participate in something and they landed with us and so we did a lot of learning in the process about be tests we wrote features and automated them for the drupal 6 version and
one of the things that we learned and that we're going to talk about more is that actually no one person had any idea what all of the functionality of drupal.org was more than that they didn't know who had the permission to change that functionality
in the process of moving from Drupal 6 to Drupal 7 so it was a question of having four of us really in and a few other people look at Drupal 6 and describe what it did whether that was right or not and then get that stuff automated and as the Drupal 7 site
became more available to then apply those tests to Drupal 7 and where they didn't work anymore update them so we did that and we worked on them until about September of 2012 for Drupal 6 and then 7 was announced to be imminent at that time so we took all
of our effort and put it into porting the test to Drupal 7 we completely abandoned working on any of the Drupal 6 testing in January and only lightly worked on the Drupal 7 tests so in the last couple of months funded by the triple association I've been
making sure that those tests are reliable and robust and functional in order to support the d7 upgrade among other QA tasks for the d7 upgrade so these are some of the people who worked on it Jonathan hedstrom who's the author of the Drupal extension which
came out of this project that's an extension to the testing tools themselves folks from capgemini and folks from a company called QED 42 who are helping now so these are all people who've been involved in the effort and it's currently back to a
[ ... ]
Nota: se han omitido las otras 1.790 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.