Posted by grendzy on December 4, 2008 at 6:50am
5 followers
Jump to:
| Project: | Project Issue File Review |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed (fixed) |
Issue Summary
The "detailed results" page shows the number of failures for each test class, but does not reveal which test methods failed, nor what their error messages were. Is there a way to obtain these details?
Normally, I could get this information by re-running the tests locally. However with the issue I'm working now, I can't reproduce the failures. All the tests pass just fine an my workstation.
Or, is there documentation anywhere that describes the specific server configuration used on the test slaves, so I might attempt to reproduce the failures myself?
Thanks!
Comments
#1
moving to the right queue
#2
+1 and subscribing
#3
Could you post the specific issue your having trouble with?
Secondly the original design was to collect all the minute detailed information the SimpleTest spits out, but it places a very large load on the database and testing slaves. It actually was hosing the original system. Because of that we decided against it.
I think having a page describing the server setup of each of the slaves, and or standardizing it would be a good idea. This we have talked about and are working towards. Additionally #337795: Test patches on multiple environments.
#4
Here's the result page I'm struggling with:
http://testing.drupal.org/pifr/file/1/278770_0.patch
I'm doing a bunch of tests for file_create_url(). Basically the tests manipulate the value of 'file_directory_path', and 'file_downloads', and test a bunch of different conditions Here's an example of the beginning of one test:
<?php// The assumption is that the temp directory is outside the DocumentRoot, exists, and is writeable
variable_set('file_directory_path', file_directory_temp(). '/' . uniqid() . '_files');
variable_set('file_downloads', FILE_DOWNLOADS_PRIVATE);
mkdir(file_directory_path());
$file = $this->createFile();
?>
My hunch is that it's permissions issue, or perhaps something else platform-specific. Are any of the test slaves running windows?
#5
Due to the nature of the testing framework the slave cannot run Windows. Currently they all run some form of Linux (Ubuntu, Centos, and Fedora are the main ones). I suppose it could be a permission issue with temp directory?
I'll check into it the next time I have a chance.
#6
Guess I can't blame windows then. ;) Thanks for checking in to it. In the meantime, I may just resubmit the patch to see what happens. Thanks!
#7
Any chance you could send me the full test results for this patch?
http://testing.drupal.org/pifr/file/1/278770_1.patch
Thanks!
#8
#9
#10
Committed.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.