User history - 6.x-1.x

Test status
StatusResult
Last receivedThu, 03/08/2012 - 10:05:39
Last requestedThu, 03/08/2012 - 10:06:19
Last testedThu, 03/08/2012 - 10:06:25
Test count2
Environment status
MySQLpass
Code reviewfail
Overall Resultpass
Branch information
Identifier6.x-1.x
ProjectUser history
LinkProject information
SummaryPASSED: [[SimpleTest]]: [MySQL] 0 pass(es); [[Coder]]: [Code review] 15 minor(s), 0 critical(s), and 23 normal(s).
Details

MySQL

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a Drupal installation failure
  8. Detect a test run failure
  9. Detect a failing test
  10. Complete test suite with all tests passing

Code review

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a review run failure
  8. Detect coder flags
    Ensure that your code follows the Drupal standard and passes a coder review.
  9. Complete coder review with all passed
15 minor(s), 0 critical(s), and 23 normal(s)

Non-pass

Test nameMinorCriticalNormal
Expanduser_history.admin.inc203
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.admin.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.admin.inc15N/A
indent secondary line of comment one space Otheruser_history.admin.inc57N/A
Separate comments from comment syntax by a space.Otheruser_history.admin.inc59N/A
indent secondary line of comment one space Otheruser_history.admin.inc73N/A
Expanduser_history.install003
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.install2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.install16N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.install23N/A
Expanduser_history.module13017
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.module2N/A
Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs)Otheruser_history.module34N/A
Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs)Otheruser_history.module35N/A
There should be no trailing spacesOtheruser_history.module77N/A
indent secondary line of comment one space Otheruser_history.module94N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module126N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module126N/A
indent secondary line of comment one space Otheruser_history.module127N/A
indent secondary line of comment one space Otheruser_history.module144N/A
indent secondary line of comment one space Otheruser_history.module156N/A
The $message argument to watchdog() should NOT be enclosed within t(), so that it can be properly translated at display time.Otheruser_history.module167N/A
indent secondary line of comment one space Otheruser_history.module180N/A
indent secondary line of comment one space Otheruser_history.module197N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOtheruser_history.module201N/A
indent secondary line of comment one space Otheruser_history.module209N/A
indent secondary line of comment one space Otheruser_history.module231N/A
Function documentation should be less than 80 characters per line.Otheruser_history.module245N/A
Function summaries should be one line only. (Drupal Docs)Otheruser_history.module245N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module246N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module246N/A
Separate comments from comment syntax by a space.Otheruser_history.module264N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module277N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module277N/A
indent secondary line of comment one space Otheruser_history.module278N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module300N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module300N/A
indent secondary line of comment one space Otheruser_history.module301N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module330N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module331N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOtheruser_history.module334N/A

All

Test nameMinorCriticalNormal
Expanduser_history.admin.inc203
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.admin.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.admin.inc15N/A
indent secondary line of comment one space Otheruser_history.admin.inc57N/A
Separate comments from comment syntax by a space.Otheruser_history.admin.inc59N/A
indent secondary line of comment one space Otheruser_history.admin.inc73N/A
Expanduser_history.install003
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.install2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.install16N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Otheruser_history.install23N/A
Expanduser_history.module13017
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Otheruser_history.module2N/A
Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs)Otheruser_history.module34N/A
Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs)Otheruser_history.module35N/A
There should be no trailing spacesOtheruser_history.module77N/A
indent secondary line of comment one space Otheruser_history.module94N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module126N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module126N/A
indent secondary line of comment one space Otheruser_history.module127N/A
indent secondary line of comment one space Otheruser_history.module144N/A
indent secondary line of comment one space Otheruser_history.module156N/A
The $message argument to watchdog() should NOT be enclosed within t(), so that it can be properly translated at display time.Otheruser_history.module167N/A
indent secondary line of comment one space Otheruser_history.module180N/A
indent secondary line of comment one space Otheruser_history.module197N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOtheruser_history.module201N/A
indent secondary line of comment one space Otheruser_history.module209N/A
indent secondary line of comment one space Otheruser_history.module231N/A
Function documentation should be less than 80 characters per line.Otheruser_history.module245N/A
Function summaries should be one line only. (Drupal Docs)Otheruser_history.module245N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module246N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module246N/A
Separate comments from comment syntax by a space.Otheruser_history.module264N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module277N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module277N/A
indent secondary line of comment one space Otheruser_history.module278N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module300N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Otheruser_history.module300N/A
indent secondary line of comment one space Otheruser_history.module301N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module330N/A
If you define a @param or @return, you should document it as well.Otheruser_history.module331N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOtheruser_history.module334N/A