I've found one use case, that wasn't covered by initial plan.

1. Installation is possible only with PHP v.7 because of "random_int" function, used in added code.

Removed test file.

Fixed API difference causing a notice (and non-working cache), when attempting to get several keys at once using get method.

In D340#7001, @erik wrote:

2. When testing, I tried to add more rows to "Regional" grid, and, after 5-6 rows added by standard in-portal grid interface, i got errors.
   

This must be perception issue with that specific icon and fact, that it has own transparent margins that aren't aligned. Below I've attached 2 images to demonstrate the issue:

1. Updated demo data of "default" and "simple" themes to make them searchable immediately after installation.
2. Improved trimming logic, when combining content block data to end up in less trailing spaces.
3. Fixed notice during search about missing PageContent field of categories.

Fixed Firefox icon alignment issues on large (>10 rows) grids

Not reopening, but test plan have issues:

In D351#6952, @alex wrote:

Test plan requested updates:

• cover auto-usage of Memcached on PHP 7+, when Memcache is configured to be used
• cover usage of new caching backend (all public methods via corresponding kApplication facade methods (e.g. MemcachedCacheHandler::add maps to kApplication::addCache and so on)
  
  I'm not able to test any further, because all data set to cache will auto-expire immediately.

Test plan requested updates:

No matter how I try to follow test plan I'm get getting pages used in test:

Test plan not updated to cover searching through large amount of text.

You're only testing new code, but existing code isn't tested. The test plan should also cover, that shipping limitations are applied correctly.

Also the test plan doesn't cover a glimpse of what's actually being checked in code. To test what you've done you need to manually change values of corresponding setting via ini_set (to cover each if/else created) before calling new code from startup.php to assert that result is desired number of bytes.

Also update test plan to cover cases, when we're searching last word in large text (more then 65 KB).

In D243#6845, @erik wrote:

No strlen error in debugger from changed ValidateRange method. 'FirstName' test value detected as invalid in other validation method (ValidateType) and not passed to ValidateRange method.

The inline comments with NOTE: battle against malformed dates entered by user line above them are actually UX discovered issues, that weren't part of original task, but without fixing them user would be as confused as now thinking that date entered in incorrect format is actually working as filter, when it's not.

Please also separate test plan into smaller fragments to ease testing. One test plan per each In-Portal module would be great.

After discussing with reviewer figured out, that test plan needs to be changed to test, that correct Styles dropdown works in all themes and not advanced theme only.

In Firefox checkbox table cell height is slightly larger (by 0.23 px) then data row height resulting in visible vertical checkbox column offset for grids with 10+ rows. Needs to be addressed via CSS somehow.