Test plan updated to compensate for the found error. Turns out that include_path field option is mandatory, when kPictureFormatter is used without upload_dir option.
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
May 20 2017
May 18 2017
May 17 2017
Please test again, because last time you've forgot to test all (skipped 1st line of test plan).
May 11 2017
May 10 2017
Some issues on test plan:
9.5.C. - No clickable General tab on label editing screen. Button Save used for test.
11.4 - no Label field in the theme editing form (Name field is there)
20.6 - Article excerpt do not use standard inp_edit_textarea control, so it can't be tested this way without some additional changes.
May 2 2017
May 1 2017
Apr 30 2017
Apr 29 2017
Apr 25 2017
Also update test plan:
Apr 22 2017
Apr 14 2017
Apr 12 2017
Please add corresponding discussion in Confluence.
Some of requested changes might need changing the test plan as well.
Apr 11 2017
Apr 2 2017
Mar 31 2017
Mar 29 2017
Mar 28 2017
Also support scrolling of search settings.
Mar 27 2017
Mar 21 2017
Don't attempt to replace parameters in the error message, when none were given.
Mar 19 2017
Mar 15 2017
For date columns use export format during import as well.
Mar 13 2017
Mar 2 2017
Mar 1 2017
Test plan is way off.
Feb 28 2017
After http://jira.in-portal.org/browse/INP-1683 is implemented:
Feb 24 2017
Changes, that are needed after reviewing screenshots attached to the JIRA issue:
- test plan for regressive testing is missing. Since PHP code affecting Front-End was changed the test plan must also include Front-End
- include browser screenshot of each process step so that we can assert texts and overall look
- add login/forgot_password_reset_confirm.tpl, that would:
- be similar to front-end in terms, that it will be showing message to user
- will automatically redirect to index template after 5 seconds
- change login/forgot_password_reset.tpl so that next_template hidden field would lead to login/forgot_password_reset_confirm instead of index
Feb 19 2017
Feb 13 2017
Feb 10 2017
Decided not to change anything after all, because we're not insisting on #PARENT# usage in hooks, but recommending it.
Handle hook processing deprecation in kUnitConfigReader::parseHooks method using kUtil::deprecatedArgument('kApplication::registerHook', ...).