Campaign Monitor - 7.x-1.x | Drupal Quality Assurance

Latest changes

So Long and Thanks for all the Tests

1 week 1 day ago

Support

In case of troubles

check the FAQ. Please make sure you've tried the test locally.
search known testbot issues and then create a new issue if yours isn't there already. Please give a link to the test.

Test client logs

No clients to display.

Campaign Monitor - 7.x-1.x

Test status

Status	Result
Last received	Wed, 02/08/2012 - 20:32:37
Last requested	Wed, 02/08/2012 - 20:37:23
Last tested	Wed, 02/08/2012 - 20:37:33
Test count	4

Environment status

MySQL	pass
Code review	fail

Overall Result	pass

Branch information

Identifier	7.x-1.x
Project	Campaign Monitor
Link	Project information

Event logView entire log

ID	Message	Timestamp
3154848	Result retrieved by project client.	4 years 6 days ago
2971028	Result retrieved by project client.	4 years 2 weeks ago
2971023	Result retrieved by project client.	4 years 2 weeks ago
2971013	Result received from test client #.	4 years 2 weeks ago
2971008	Requested by test client #.	4 years 2 weeks ago
2971003	Result received from test client #.	4 years 2 weeks ago
2970998	Requested by test client #.	4 years 2 weeks ago
2970913	Test request received.	4 years 2 weeks ago
2970793	Result retrieved by project client.	4 years 2 weeks ago
2970778	Result retrieved by project client.	4 years 2 weeks ago

SummaryPASSED: [[SimpleTest]]: [MySQL] 0 pass(es); [[Coder]]: [Code review] 0 minor(s), 4 critical(s), and 105 normal(s).

Details

MySQL
Code review

MySQL

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a Drupal installation failure
Detect a test run failure
Detect a failing test
Complete test suite with all tests passing

Review log

Code review

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a review run failure
Detect coder flags
Ensure that your code follows the Drupal standard and passes a coder review.
Complete coder review with all passed

0 minor(s), 4 critical(s), and 105 normal(s)

Non-pass

Test name

Minor

Critical

Normal

campaignmonitor.module

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	9	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	27	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	48	N/A
Administrative menu items should have a description.	Other	campaignmonitor.module	63	N/A
Administrative menu items should have a description.	Other	campaignmonitor.module	72	N/A
Administrative menu items should have a description.	Other	campaignmonitor.module	117	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	251	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	campaignmonitor.module	258	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	262	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	264	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	265	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	282	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	290	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.module	332	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor.module	381	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	414	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.module	417	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor.module	428	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor.module	431	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor.module	432	N/A

campaignmonitor_list_stats.tpl.php

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	campaignmonitor_list_stats.tpl.php	-1	N/A

includes/campaignmonitor.admin.inc

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor.admin.inc	9	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor.admin.inc	12	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.admin.inc	34	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	campaignmonitor.admin.inc	35	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.admin.inc	42	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	campaignmonitor.admin.inc	43	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.admin.inc	89	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor.admin.inc	116	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor.admin.inc	129	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor.admin.inc	132	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor.admin.inc	133	N/A

includes/campaignmonitor_lists.admin.inc

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	10	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	13	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	98	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	99	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	101	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor_lists.admin.inc	178	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	289	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	294	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	295	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	296	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	332	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	333	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	334	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	335	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	335	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor_lists.admin.inc	352	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	358	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	359	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	383	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor_lists.admin.inc	409	N/A
Function documentation should be less than 80 characters per line.	Other	campaignmonitor_lists.admin.inc	421	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	421	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	424	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	425	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	426	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	442	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	446	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	447	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	455	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	459	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_lists.admin.inc	470	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	487	N/A
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_lists.admin.inc	488	N/A

includes/campaignmonitor_stats.admin.inc

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	campaignmonitor_stats.admin.inc	-1	N/A

lib/campaignmonitor.class.inc

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	campaignmonitor.class.inc	11	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	152	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	166	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	179	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	180	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	194	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	campaignmonitor.class.inc	348	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	539	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	648	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	650	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	655	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	668	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	669	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	674	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	676	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	680	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	696	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	707	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	708	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	722	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	campaignmonitor.class.inc	723	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	725	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	729	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	731	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	748	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	751	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	760	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	773	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	775	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	780	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	798	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	campaignmonitor.class.inc	801	N/A

modules/campaignmonitor_registration/campaignmonitor_registration.module

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_registration.module	22	N/A
table names should be enclosed in {curly_brackets}	Other	campaignmonitor_registration.module	49	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	campaignmonitor_registration.module	49	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_registration.module	56	N/A

modules/campaignmonitor_user/campaignmonitor_user.module

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	campaignmonitor_user.module	54	N/A
table names should be enclosed in {curly_brackets}	Other	campaignmonitor_user.module	86	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	campaignmonitor_user.module	86	N/A
The $message argument to drupal_set_message() should be enclosed within t() so that it is translatable.	Other	campaignmonitor_user.module	97	N/A
Function summaries should be one line only. (Drupal Docs)	Other	campaignmonitor_user.module	104	N/A

All