Improve and expand Drupal.org testing beyond its current borders:
- Improve testing reliability and capability
- Test on additional environments (pgsql, sqlite, Microsoft, Selenium)
- Improve documentation and understanding of our code, infrastructure, and capabilities.
- Make PIFR more deployable in environments outside D.O.
Testing Infra Evolution - Requirements
Purpose
This page is intended as a collection point for requirements for the next generation of Drupal.org's automated testing environment. Please feel free to update this page with your own thoughts and ideas, and help contribute to the requirements which will define the next (r)evolution of Drupal's testing infrastructure.
Read more
D7 Drupal.org Port & Testbot Evolution Strategy
DOCUMENT PURPOSE
The purpose of this document is to outline a proposed roadmap for Drupal testbot evolution, as discussed during the testbot evolution sprint at DrupalCon Denver on Friday, March 23rd, 2012. Participating in the discussion were Jeremy Thorson, Jimmy Berry, and Randy Fay. This proposal is also influenced by additional consideration and input provided by participants in the TestBot BoF held one day earlier.
Read moreThoughts on Drupal Testbot Evolution
Note: This is a copy of a blog post original posted on March 20th, 2012; with the original located at http://jthorson.doesdrupal.com/thoughts-on-testbot-evolution ... it is being reposted here in the interest of consolidating the information on Drupal.org infrastructure, and to improve discoverability by any potentially interested parties.
Having spent the better half of the last year within the PIFT/PIFR issue queues, chasing the holy grail of sustained testbot stability, I find myself reaching a bit of a crossroads.
Read more
Upgrade Drupal.org to Drupal 7 Sprint!
The week of April 23 - April 27, the Drupal Association is sponsoring a sprint, hosted by the Oregon State University Open Source Lab, to upgrade Drupal.org from Drupal 6 to Drupal 7!
The sprint will be mainly focused on the following areas, and the following attendees will be there:
Read moreDrupal.org Office Hours
Come to Drupal.org office hours to share what you're working on and help us come up with the weekly drupal.org hit list!
Stop by #drupal-infrastructure from 11am to 12pm Pacific Time (18:00 - 19:00 UTC).
Move all core Drupal files into /core folder
On November 1, 2011, all Drupal 8.x core files will be moved into a /core folder. This will break nearly every patch in the 8.x queue, requiring them at least to be re-rolled against the updated directory structure.
After that date, backporting 8.x patches to 7.x will no longer be trivial.
Dries announced in #22336-254:
Read moreLondon Automated Testing/Project Dependency Sprint Plan 26 Aug 2011
The Project Dependency module is deployed and enabled on drupal.org, with initial dependencies built! Now we have to get to the next step, deploying the PIFT changes that go with it.
IRC: #drupal-testing
- Our key #1 goal for the day is to get dependencies stable and deployed, see Project Dependency.
- Fix additional project dependency issues with memory limit.
London Project Dependency Sprint Friday
I'd love to do a code sprint on testing Friday at Drupalcon London.
The most important outcome would be deployment of Project Dependency and the related PIFT, PIFR, and Project module changes.
What we need to do to accomplish this:
- Set up a test environment (PIFT, QA.scratch + testbot) demonstrating dependencies working.
- Get the new PIFR version deployed, assuming it can be done without a PIFT change.
- Get the deploy issue RTBC'd and perhaps deployed.
New docs page, and updated project pages
I wanted to point possible contributors to a new low-level testing infrastructure doc page, http://drupal.org/automated-testing - Although this is incomplete and probably incorrect, it's a starting place for documenting our testing infrastructure. I invite you to improve it.
Automated Coder Reviews for New Project Applications - Planning/Development
This wiki page has been set up to continue the 'Automated Coder' discussion initially started at http://groups.drupal.org/node/155084#comment-517764.
Read moreOutstanding Progress on Selenium/Simpletest Integration
I want to make sure that everybody in these groups knows about the fantastic simpletest + selenium integration work that ygerasimov has been doing. I just tested out his Selenium module (7.x) and it worked fine for me.
Here's what I did:
- Install Selenium module and start Selenium Server as described in the INSTALL.txt.
- Installed the Selenium Test Example sandbox for sample tests.
Testbots on OSU-OSL Supercell
I posted about the testbots being on the OSUOSL Supercell over at http://randyfay.com/node/99.
-Randy
Testing Test System Code Before Deploying
One of the problems we've always had that delays deployment of PIFR and PIFT code is that it has been hard to test. But now we have a workable test environment, consisting of three parts:
- A drupal.org clone, http://rfay.redesign.devdrupal.org, housed on stagingvm.drupal.org. (This is one of the new tricked out development sites that are now available to people who want to improve drupal.org)
- http://qa.scratch.drupal.org, housed on stagingvm.
- Testbots as needed can be spun up either as local VMs and configured to pair with qa.
Test Suite Performance
I was trying to gauge what the best setup for a PIFR node is, and I noticed that this page (http://qa.drupal.org/node/62) seemed way out of date, so I ran some tests of my own. Here I was trying to figure out a couple of things:
- Which concurrency setting is best?
- How does performance improve with number of cores
For testing, I used two separate PIFR nodes running in KVM virtual machines with the following specs:
CPUs are Opteron 6172, 2.1 Ghz
2 GB RAM
Local disk (10K SAS)
Running Debian Squeeze 64-bit, installed PIFR using DamZ's puppet setup
My results were as follows:
Read moreTest environment for 6.x-2.x is ready
We have a test environment available now to test the new code that is ready to be deployed and solves the problems with 6.x core patches and a number of contrib problems. It does not solve the problem with loading contrib dependencies. That's our next task.
The drupal.org copy is at http://rfay.redesign.devdrupal.org. Follow the instructions on the basic auth popup to get in (drupal/drupal).
You'll need a password to get in there unfortunately (to log into the drupal.org copy itself). Please contact me on IRC or via the contact page and I'll give you your account password.
Read morePlan for merging 6.x-3.x and master branches of PIFT and PIFR
boombatower, DamZ, and I talked tonight about how to catch up to HEAD/master on PIFT and PIFR.
boombatower says there are protocol changes that have been implemented on the PIFR side but not PIFT, and probably HEAD of each won't talk to each other.
The plan:
- rfay will create an experimental branch and try to merge all the 6.x-3.x work (git migration, since 6.x-2.2) into the former HEAD (master).
Regular updates to qa.drupal.org status page
I noticed that issues with queued patches were not being updated with test results, so naturally, I visited qa.drupal.org to see what was the problem.
Not only is the statistics page (still) returning a 500 server error, but the most recent "News" item is over a year old.
Read moreDrupalcon Chicago PIFR/PIFT Code Sprint
I'm planning to sprint Friday on PIFR/PIFT (our d.o testing infrastructure) and would love to have everybody involved (or who wants to be involved) in there.
Here are things I think we could do:
- Merge boombatower's work on HEAD with the 3.x work done for the Git migration.
- Make testing work for the 8.x branch
Building Selenium Tests for Drupal.org
The steps involved in taking forward the Selenium test for Drupal.org initiative:
Link to drupal.org issue queue: http://drupal.org/node/991040
- Identifying a groups of people interested in building Selenium test-cases
- Working on Identifying critical tests
- Writing tests
- Working with the infrastructure team to run these tests
If you are interested in building Selenium tests and supporting the same, please add you name and the area of support.
Implementers:
Looking for Students
We are currently seeking students interested in learning about our AWS testing implementations. The primary objective is to create a curriculum that will help educate others understand the methods utilized by the Drupal infrastructure to support it's automated testing in the Amazon cloud. This is a prime opportunity for you to become involved in Drupal and help create positive learning materials to help others understand the benefits of Amazon cloud services as they apply to Drupal.
Read more