New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI unit tests #4189
Comments
@capedfuzz the omni fixture broke the UI tests: https://travis-ci.org/piwik/piwik-ui-tests |
In 57bf5d0: Refs #4189, bug fixes for dashboard & changes to make dashboard UI tests possible. Includes:
|
In 8a525ad: Refs #4189, more work getting UI tests to pass and adding admin screenshots, including:
|
In 5c66663: Refs #4189, adding Overlay screenshot tests:
|
UI Unit Tests Project Summary:
Intended Outcomes
Next Steps:
Room for improvement:
|
…run every commit even when the Integration tests fail. This will help know exactly which commit introduced a regression.
…bines all other fixtures.
…wDataTable. Refactored capture.js to make new type of testing possible.
…CSS so tests look right.
…nfig option code, placed OmniFixture into a namespace, removed PHP screenshot testcase classes and added fixture for use w/ JavaScript screenshot tests.
…nd popover issue in phantomjs (modifying window.location.href directly erases JavaScript state for page even if the URL is the same) and tweak user creation in test fixture setup.
…tual & mock data access class to DBStats, fix bug that occurs when deleting merged assets that do not exist and fix diffviewer generation regression (expected URL was incorrect).
…tes for UI tests for site selector and make site selector has a margin top in UI tests.
…iod selector, add periodSelector CSS class to period selector.
…oardSettingsControl() action output for tests, make sure last dashboard always overwritten by UI test start.
…oard UI tests possible. Includes: - fix for bug where top controls not displayed correctly when dashboard is displayed in a widget iframe. - do not display dashboard manager after dashboard action selected. - truncate tables when running UI tests w/ --persist-fixture-data so existing database data won't be used if the fixture setup didn't complete before. - do not create super user more than once in Fixture. - don't include Test_Piwik_Fixture_CustomAlerts in omni fixture. - make sure UITestFixture executes the correct code every time regardless of whether --persist-fixture-data isn't used. - add mouseup/mousedown events to screenshot testing page rendere. - add ability to call controller methods in screenshot tests and fix API calling mechanism.
…n for tests, rewrite proxy/index.php to use hooks for config instead of disabling dispatch.php and remove no longer used config override code.
…dmin screenshots, including: - make updatetoken.php use TestingEnvironment in testmode, - allow persisted fixture to be dropped using new --drop command line option (for ui test runner), - fix debugging mistake in realtime map, fix merge error in empty.twig, - make sure Fixture prints to screen only for UI test setup, re-enable CustomAlerts fixture in OmniFixture, - make sure forced now value for realtime map is constant, - use *.getDatabaseConfig events to override database name in TestingEnvironment - use TestingEnvironment in proxy/piwik.php - add wait() method to screenshot testing framework's PageRenderer - hide current UTC time in manage websites admin screenshot
- Make 'idsite' parameter in certain Overlay URLs 'idSite'. - Make sure Overlay sidebar has width so screenshot test framework can find position. - Add overlay test site so Overlay can be loaded in phantomjs. - Remove createSuperUser call from TrackerTest (done in Fixture setUp). - Make sure piwik.js link is created for screenshot tests & make sure the test environment JSON file is loaded after the database is setup. - Modify logic that waits for images to load in screenshot testing framework's page renderer to wait for CSS image URLs.
We should increase our JavaScript code coverage by adding unit tests for individual UI controls. To do this, we need to:
The text was updated successfully, but these errors were encountered: