VKontakte CrossPoster - 7.x-1.x

Test status
StatusResult
Last receivedThu, 01/26/2012 - 13:59:36
Last requestedThu, 01/26/2012 - 14:20:49
Last testedThu, 01/26/2012 - 14:20:58
Test count2
Environment status
MySQLpass
Code reviewfail
Overall Resultpass
Branch information
Identifier7.x-1.x
ProjectVKontakte CrossPoster
LinkProject information
SummaryPASSED: [[SimpleTest]]: [MySQL] 0 pass(es); [[Coder]]: [Code review] 9 minor(s), 0 critical(s), and 71 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
9 minor(s), 0 critical(s), and 71 normal(s)

Non-pass

Test nameMinorCriticalNormal
Expandvkxp.admin.inc108
MessageGroupFilenameLineFunctionStatus
Function summaries should be one line only. (Drupal Docs)Othervkxp.admin.inc9N/A
Arrays should be formatted with a space separating each element and assignment operatorOthervkxp.admin.inc39N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.admin.inc58N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc59N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.admin.inc75N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc76N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc83N/A
There should be no trailing spacesOthervkxp.admin.inc100N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.admin.inc157N/A
Expandvkxp.api.php204
MessageGroupFilenameLineFunctionStatus
There should be no trailing spacesOthervkxp.api.php7N/A
There should be no trailing spacesOthervkxp.api.php8N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.api.php10N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php12N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php14N/A
Expandvkxp.install201
MessageGroupFilenameLineFunctionStatus
There should be no trailing spacesOthervkxp.install16N/A
There should be no trailing spacesOthervkxp.install17N/A
Use the matching Drupal theme functions, not raw HTML.Othervkxp.install22N/A
Expandvkxp.module4058
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othervkxp.module-1N/A
Administrative menu items should have a description.Othervkxp.module29N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.module30N/A
Administrative menu items should have a description.Othervkxp.module42N/A
Administrative menu items should have a description.Othervkxp.module51N/A
indent secondary line of comment one space Othervkxp.module80N/A
indent secondary line of comment one space Othervkxp.module81N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module129N/A
If you define a @param or @return, you should document it as well.Othervkxp.module130N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module130N/A
There should be no trailing spacesOthervkxp.module173N/A
There should be no trailing spacesOthervkxp.module181N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module225N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module238N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module239N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module240N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module241N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module242N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.module245N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module249N/A
If you define a @param or @return, you should document it as well.Othervkxp.module250N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module250N/A
If you define a @param or @return, you should document it as well.Othervkxp.module251N/A
If you define a @param or @return, you should document it as well.Othervkxp.module276N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module291N/A
If you define a @param or @return, you should document it as well.Othervkxp.module292N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module292N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module317N/A
If you define a @param or @return, you should document it as well.Othervkxp.module318N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module318N/A
If you define a @param or @return, you should document it as well.Othervkxp.module319N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module319N/A
If you define a @param or @return, you should document it as well.Othervkxp.module320N/A
Function documentation should be less than 80 characters per line.Othervkxp.module320N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module349N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module355N/A
If you define a @param or @return, you should document it as well.Othervkxp.module356N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module356N/A
If you define a @param or @return, you should document it as well.Othervkxp.module357N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module357N/A
If you define a @param or @return, you should document it as well.Othervkxp.module358N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module358N/A
If you define a @param or @return, you should document it as well.Othervkxp.module359N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module387N/A
If you define a @param or @return, you should document it as well.Othervkxp.module388N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module388N/A
If you define a @param or @return, you should document it as well.Othervkxp.module389N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module389N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module406N/A
If you define a @param or @return, you should document it as well.Othervkxp.module407N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module407N/A
If you define a @param or @return, you should document it as well.Othervkxp.module408N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module429N/A
If you define a @param or @return, you should document it as well.Othervkxp.module430N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module430N/A
If you define a @param or @return, you should document it as well.Othervkxp.module431N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module431N/A
If you define a @param or @return, you should document it as well.Othervkxp.module432N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module442N/A
If you define a @param or @return, you should document it as well.Othervkxp.module443N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module443N/A
If you define a @param or @return, you should document it as well.Othervkxp.module444N/A

All

Test nameMinorCriticalNormal
Expandvkxp.admin.inc108
MessageGroupFilenameLineFunctionStatus
Function summaries should be one line only. (Drupal Docs)Othervkxp.admin.inc9N/A
Arrays should be formatted with a space separating each element and assignment operatorOthervkxp.admin.inc39N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.admin.inc58N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc59N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.admin.inc75N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc76N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.admin.inc83N/A
There should be no trailing spacesOthervkxp.admin.inc100N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.admin.inc157N/A
Expandvkxp.api.php204
MessageGroupFilenameLineFunctionStatus
There should be no trailing spacesOthervkxp.api.php7N/A
There should be no trailing spacesOthervkxp.api.php8N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.api.php10N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php12N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.api.php14N/A
Expandvkxp.install201
MessageGroupFilenameLineFunctionStatus
There should be no trailing spacesOthervkxp.install16N/A
There should be no trailing spacesOthervkxp.install17N/A
Use the matching Drupal theme functions, not raw HTML.Othervkxp.install22N/A
Expandvkxp.module4058
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othervkxp.module-1N/A
Administrative menu items should have a description.Othervkxp.module29N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othervkxp.module30N/A
Administrative menu items should have a description.Othervkxp.module42N/A
Administrative menu items should have a description.Othervkxp.module51N/A
indent secondary line of comment one space Othervkxp.module80N/A
indent secondary line of comment one space Othervkxp.module81N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module129N/A
If you define a @param or @return, you should document it as well.Othervkxp.module130N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module130N/A
There should be no trailing spacesOthervkxp.module173N/A
There should be no trailing spacesOthervkxp.module181N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module225N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module238N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module239N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module240N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module241N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module242N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSEOthervkxp.module245N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module249N/A
If you define a @param or @return, you should document it as well.Othervkxp.module250N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module250N/A
If you define a @param or @return, you should document it as well.Othervkxp.module251N/A
If you define a @param or @return, you should document it as well.Othervkxp.module276N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module291N/A
If you define a @param or @return, you should document it as well.Othervkxp.module292N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module292N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module317N/A
If you define a @param or @return, you should document it as well.Othervkxp.module318N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module318N/A
If you define a @param or @return, you should document it as well.Othervkxp.module319N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module319N/A
If you define a @param or @return, you should document it as well.Othervkxp.module320N/A
Function documentation should be less than 80 characters per line.Othervkxp.module320N/A
Functions should be called with no spaces between the function name and opening parenthesesOthervkxp.module349N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module355N/A
If you define a @param or @return, you should document it as well.Othervkxp.module356N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module356N/A
If you define a @param or @return, you should document it as well.Othervkxp.module357N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module357N/A
If you define a @param or @return, you should document it as well.Othervkxp.module358N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module358N/A
If you define a @param or @return, you should document it as well.Othervkxp.module359N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module387N/A
If you define a @param or @return, you should document it as well.Othervkxp.module388N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module388N/A
If you define a @param or @return, you should document it as well.Othervkxp.module389N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module389N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module406N/A
If you define a @param or @return, you should document it as well.Othervkxp.module407N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module407N/A
If you define a @param or @return, you should document it as well.Othervkxp.module408N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module429N/A
If you define a @param or @return, you should document it as well.Othervkxp.module430N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module430N/A
If you define a @param or @return, you should document it as well.Othervkxp.module431N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module431N/A
If you define a @param or @return, you should document it as well.Othervkxp.module432N/A
Function summaries should be one line only. (Drupal Docs)Othervkxp.module442N/A
If you define a @param or @return, you should document it as well.Othervkxp.module443N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othervkxp.module443N/A
If you define a @param or @return, you should document it as well.Othervkxp.module444N/A