- πΊπ¦Ukraine AstonVictor
I'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks
Add test cases for testing the functionality of the module.
Most useful feature is the search restrictions and this is also requires the most indepth knowledge of Drupal to implement.
Personally, I was going to tackle this from the ground up (as opposed to a pure port / coder like upgrade). If you take this approach, you could do test driven development (the best, but slowest), and tackle the various components 1 by 1.
Search user permissions & query alter to exclude
Individual node exclusions (and migration support for D7 - D8)
Then the various other bits from the forms. Very roughly, these fall into the following categories.
Search limits
Search labels
Search form alters
But if you have no idea of what a query alter is, I'd definitely reverse this order, form alters are the easiest things to do in Drupal.
Also easy for adding / learning the testing API. Very repetitive tests for
* does the std Drupal search form element show unaltered without settings
* does the admin settings FAPI element show (redundant as the save check would also test this)
* does it save a value change correctly
* does the change change the front end search form
Only slight complication it that you need to consider users that can
* not see the form (not worth tests)
* can only access the basic search form
* can access the advanced search form
Create sub tasks for each test scenario and post the patch there.
None
None
None
Resources :
https://www.drupal.org/simpletest-tutorial-drupal7 β
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks