Building further on top of the existing Test Cases in the file block_class.test and following up with #2110593: Reintroduce Features integration in 2.x branch, I just realized there were no Automated Test Cases yet, to enforce compatibility and check from code whether the integration of Block Class with Features/FE Block would work as expected:

Test Cases:

  • Import the configuration of a block by enabling a feature exported with Features/FE Block.
  • Display the block and check for its exported CSS classes.
  • Modify block's CSS classes, check they display as expected and that the imported feature with Block's configuration is Overridden.
  • Revert the feature and check again for expected classes.

 
Please let me know if you would have any questions, objections, comments, suggestions, recommendations or concerns on any aspects of this feature request, I would be glad to provide more information or explain in more details.

Any questions, feedback, testing, changes, ideas or recommendations would be highly appreciated.
Thanks to all in advance.

Comments

DYdave’s picture

DYdave CreditAttribution: DYdave commented
Status: Active » Fixed

Quick follow-up on this task:

Modified the file block_class.test to add a new Test Case Class, called BlockClassFeaturesTestCase wich performs the tests described in the issue summary:

The CSS classes and configuration of the Block "Who's online" (pretty suitable for testing since it is disabled by default, unlike "Content main" for example) were exported to a feature module called block_class_fe_block_test to serve as a Helper for the Test Case.

The Features, FE Block modules and the Block Class FE Block Integration Test Helper feature are enabled to start the serie of tests.
Since the "Who's online" Block was configured in the feature to display in the Main content region, browsing directly the home page allows checking whether CSS classes are displayed as expected: fe_block-class1 fe_block-class2 fe_block-class3.

Block CSS classes are then modified with random classes and checked again on the front page.
The status of the feature block_class_fe_block_test is also checked at this point to see if the component fe_block_settings is properly Overridden.
Lastly, the feature is reverted and checked on the front page to ensure Block's configuration has gone back to its defaults (where it was at the begginning of the test case).

I went ahead and committed the changes against the 7.x-2.x branch at 7c584ef.

I allowed myself to mark this issue as fixed for now, but feel free to re-open it, or post a new ticket, at any time if you have any further objections with this ticket or related commit 7c584ef (we would surely be happy to hear your feedback).

Please let me know if you would have any further comments, feedback, questions, issues, objections, suggestions or concerns on the commit or this feature request in general, I would be glad to provide more information or explain in more details.

Thanks in advance to everyone for your testing, reviews, feedback and comments on this issue.
Cheers!

Automatically closed -- issue fixed for 2 weeks with no activity.