Problem/Motivation

Trying to setup Automated Testing for a new project, but cannot setup. The page suggests to use the "Test Additional Branches" form, but this form is not displayed on the Automated Testing page.

new project: Commerce Credits Transaction
- Has 7.x-1.x development release.
- Has tests directory, tests listed in info file, and tests are displayed in Drupal 7.
- See "new-project" screenshot.

old project: CCK Select Other
- Has 7.x-1.x development release.
- Has tests directory, tests listed in info file, and tests are displayed in Drupal 7.
- See "old-project" screenshot.

Proposed resolution

Remaining tasks

  • Identify cause of issue/triage

User interface changes

API changes

See related issues section.

CommentFileSizeAuthor
new-project.png34.63 KBmradcliffe
old-project.png63.8 KBmradcliffe

Comments

iamEAP’s picture

iamEAP commented

Chiming in. Same is happening for me on a project that was created after the D7 upgrade.

https://drupal.org/project/project_src_github

markhalliwell’s picture

markhalliwell
Primary language English
commented

Bootstrap's doesn't even let me have access to the page:
https://drupal.org/node/259843/qa
"Access denied"

mradcliffe’s picture

mradcliffe
he/him
Primary language English
commented

Even though I can't setup the test branches, patches are going to the test bot so PIFR is probably working correctly.

jthorson’s picture

jthorson commented

For #2, this is a change within the drupal.org D7 upgrade. In D6, modules, themes, and distributions were all the same content type, while in D7, they each have their own content type. At the same time, I added a configuration setting which lets you select what project types the 'automated testing' tab should appear on. Currently, this is set to the 'project_core' and 'project_module' content types, as these were the only two which were relevant from a testbot perspective.

That said, I know that folks are toying with advanced theme projects and ways of unit-testing theme projects on the testbots, so I'm willing to re-visit this setting if presented a valid use case.

jthorson’s picture

jthorson commented
Status: Active » Fixed

Fixed in http://drupalcode.org/project/project_issue_file_test.git/commit/240cf80... and merged into BZR.

This will take effect with the next drupal.org deploy.

markhalliwell’s picture

markhalliwell
Primary language English
commented
Related issues: +#2138693: Provide UnitTests for theme, +#2138733: run-test.sh needs full path for --file

Here are the follow-up issues for theme testing

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.