Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.If we want to use this as a required tool for the D7 release cycle (which I think we ought to), then we need the code in both the module and the tests themselves clean enough that you could eat off of them. Our goal should be nothing less than core-worthy code (even though obviously we don't want to make this module part of core ;)).
This is going to be my #1 priority for the next while: coding standards compliance, bountiful comments, consistency, and so on. I want to make it as simple as possible for a new developer who's never heard of SimpleTest to dig in and start being productive.
I apologize in advance for the forthcoming pedantic patches that will be coming, which include:
- It's "SimpleTest," not "Simpletest" or "simpletest".
- We need clearer, more detailed, and corrected/updated documentation pretty much everywhere.
- Coding standards compliance for both SimpleTest module and all tests.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | simpletest_code_style.patch | 216.94 KB | cwgordon7 |
Comments
Comment #1
Rok Žlender commented+10 :) you will have to watch me, my eyes usually don't notice the diff between "". or "" . and stuff like that. Can we even tweak coder module to scan .test files.
Comment #2
vladimir.dolgopolov commentedMy 10 cents for new deweloper's sake:
I suggest to add more helper methods in SimpleTest for common uses cases.
I suggest add a parameter to this (and existed) methods to avoid a lots of asserts' output messages. If I test only page creation I wish to hide messages of sucessful user login and so on.
PS. SimpleTest is awesome
Comment #3
cwgordon7 commented+11 :) Perhaps run the whole thing through coder format?
Comment #4
cwgordon7 commentedInitial code style patch
Comment #5
KentBye commentedBoombatower and I were looking at this during the code sprint, and created a sub-issue related to this for finding a consistent naming convention for the *.test files: http://drupal.org/node/231348
Comment #6
catchComment #7
boombatower commentedDo we want comment blocks for the file that contain test description and author?
Comment #8
cwgordon7 commentedI just removed them to standardize things. But I also think it is not good practice to credit yourself after you write a simpletest.
Comment #9
catchWe should see tests being created as patches to core soon, so credits will probably happen via the commit log. Nice to have a description of the test somewhere though.
Comment #10
boombatower commentedAfter reviewing community ideas and talking with chx and Rok Žlender we have agreed upon the last convention and I have written a script to correctly name the tests.
I started a discussion about coding standards and group convention.
Comment #11
boombatower commentedChanged project name from
SimpletesttoSimpleTest.Comment #12
boombatower commentedPerformed general cleanup of SimpleTest module files: #107173.
Tests: #107174.
Comment #13
boombatower commentedCommitted several other cleanup related to coding standards which are documented there.
Comment #14
boombatower commentedAs I see it we only have to things left.
1) Get coding standards into Coder Module
2) Clean up documentaion
Comment #15
birdmanx35 commentedI'm working on the second now.
Comment #16
boombatower commentedChanged module name in
.infofile to "SimpleTest instead of "SimpleTest Module" and updated description.Comment #17
boombatower commentedFixed more naming issues is simpletest.module simpletest_menu().
http://drupal.org/cvs?commit=109535
Comment #18
boombatower commentedAdded un-install hook to remove variables.
http://drupal.org/cvs?commit=109886
Comment #19
boombatower commentedSince I seem to keep forgetting to change the version.
Comment #20
boombatower commentedThis has been completed and will stand as a record.
Comment #21
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.