#3383 - Manual release testing for major releases (ongoing)
-
By Chris Graham
- Added
- 5 views
| Identifier | #3383 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Manual release testing for major releases (ongoing) |
| Status | Open |
| Tags |
Roadmap: ongoing (custom) Roadmap: Over the horizon (custom) Roadmap: v11 final phase (custom) |
| Handling member | Deleted |
| Addon | General / Uncategorised |
| Description | These are tests to be done manually before putting out a major new release, because they represent what could have broken and gone unnoticed...
1) All screens on Sitemap load 2) All blocks render (using Add Block tool) 3) Do profiling (usually mainly xdebug) to make sure there are no serious performance regressions, particularly around unneeded code files being loaded, excessively used function calls, expensive function calls, excessive queries, expensive queries, excessive IO operations, expected caching not activating 4) The abstract file manager works, when removing addons on a non-suEXEC server 5) Working on IIS, and Web Platform package works 6) Print stylesheet 7) Test upgrading from the prior major version. Test that module/block/addon upgrade code is working as expected via the MySQL cleanup tool. It will say if tables/indices/privileges are not in the database as they are expected to be (assuming you already generated "db_meta.dat" via "data_custom/build_db_meta_file.php" on a clean install). 8) EU Cookie message works 10) APC works (can use automated test) 11) Wincache works (can use automated test) 12) APS installer works (if we've published it) 13) Embed every type of supported media with the media tag 14) Mobile preview 15) Works in Safari 16) Works in Firefox 17) Works in Edge 18) Works in IE11 19) Works on iOS, with mobile device detection 20) Works on Android, with mobile device detection 21) Social share links work 22) Magic click / context menu features work 23) Works in oldest supported PHP version 24) Works in newest supported PHP version 25) Works in oldest supported MySQL version 26) Works in newest supported MySQL version 27) Test scheduled news publishing works 28) Google reCAPTCHA working 29) Google Map addon works 30) Inline editing works 31) Twitter addon(s) work 33) Test with phpBB forum driver; run full set of automated tests 34) Test with the none forum driver (no forums and members); run full set of automated tests 35) Install test content then view the "lorem:start", "lorem:lorem" and "lorem:menus" pages to ensure blocks are working 36) Test through a full Quick Install then Setup Wizard manually 37) oEmbed works 38) Sensible error message if missing caches/lang permissions, in both installer and home page 39) Sensible error message if missing themes/default/templates_cached/EN permissions, in both installer and home page 40) Merge one test site with the default test content plus stress_test_loader content into another with no test content 41) Manually test many other non-bundled addons, as you feel comfortable doing 42) Install with XML database driver; run full set of automated tests 43) Install with safe mode; run full set of automated tests 44) Test all Comcode tags Of course run all the normal automated tests, including running all the "_"-prefixed unit tests individually. Also tests on compo.sr: i) Run accessibility testing tools on compo.sr homepage ii) Demonstratr iii) Google Analytics collection working iv) Facebook addon works v) Tapatalk addon works vi) E-mails go out correctly, including when using DKIM vii) Broken link scan with google_search_console and moz configured Also some code scanning: a) Run other lint tools (listed in _tests/codechecker/readme.txt) and see if any warning stands out as a bug b) Look for copy and pasted code, or code that duplicated due to bad git automerging... ^(?m)(.{300}).{0,3000}\1 c) OWASP Zap (https://www.zaproxy.org/) |
| Steps to reproduce | |
| Additional information | Some of this covers stuff mentioned on http://compo.sr/maintenance-status.htm
|
| Related to | #1305 - Remove 'LEGACY' code (ongoing) #1788 - Support HTML.next and ECMAScript.next (idea staging issue) |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Add something like this to _config.php (as appropriate, :
$SITE_INFO['custom_file_base'] = '/Library/WebServer/Documents/composr_demonstratr';
$SITE_INFO['custom_base_url'] = 'http://localhost/demonstratr';
Make the demonstratr under your webroot.
Once this is done, Composr will be running with the main code files in one place, and all customisations in the demonstratr folder. Composr should be called from the normal URL of your install.
This isn't actually Demonstratr, but it will trigger the same underlying segregation code, which is the complex part of it.