linux/poky.git/bitbake/lib/toaster/tests, branch uninative-1.4

bitbake: toaster: Add tests to detect if we have missing db migrations

2016-09-21T20:58:06+00:00

Based on the same test as found in patchwork by Damien Lespiau https://github.com/dlespiau/patchwork/blob/master/patchwork/tests/test_db.py (Bitbake rev: 031cb194aaa1b6cc970fed3fa0d0dbd3ebac163f) Signed-off-by: Michael Wood Signed-off-by: bavery Signed-off-by: Richard Purdie

bitbake: toaster: tests Add selenium test layer source switching layer details page

2016-09-02T17:09:50+00:00

Add selenium tests for the new layer source switching functionality on the layer details page. Edits the values for git repository and saves and then edits the details for directory information and saves. (Bitbake rev: acdfafdd753abe38a313c42e3a9d6211338b4e73) Signed-off-by: Michael Wood Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: add test for showing self-dependent task

2016-08-10T23:09:27+00:00

Toaster occasionally records a task which depends on itself. Add a test which checks that a task which depends on itself can be displayed in the task page. [YOCTO #9952] (Bitbake rev: b7a699e701785b5bd8da97b6e1b760a1c6dd05f5) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: add tests for reverting to default sort

2016-08-10T23:09:27+00:00

Add tests for ToasterTable UI table sort reverting, which can only be exercised via the browser. Check that if a table is sorted by a column, and that column is hidden, then the sort reverts to the default for the table. [YOCTO #9836] (Bitbake rev: 5b016338478d784fd048ba2baae121c3e558090c) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: fix erroneous message when test fails

2016-08-10T23:09:27+00:00

When one of the layer details tests fails (as it occasionally does, if running on a machine under heavy load, due to sync issues), the error message shown is misleading, as it is something like: "Expected 'This was imported' in ['This was imported', ...]" The string 'This was imported' is in the list shown in the message, but the message suggests it isn't. This is because the test compares the string with one list, but then uses a different list in the fail message if the comparison fails. Fix the list shown in the message about the test failing. (Bitbake rev: 34943b2278efe99c6744399e04a47cdda630468e) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: add tests for most recent builds state changes

2016-08-10T23:09:27+00:00

Add tests for the state transitions in the "most recent builds" area of the all builds page. [YOCTO #9631] (Bitbake rev: b95681cf38475903ad4f73059313dda8c0dccef6) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: add tests for build dashboard menu and summary visibility

2016-08-10T23:09:27+00:00

Test that the build dashboard only shows a menu and a build summary area if a build has properly "started" (i.e. has at least one Variable object associated with it). [YOCTO #8443] (Bitbake rev: 9e16f76fb254ae967ded6c21251243b2af9b16b6) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster-tests: add tests for build time links in the all builds page

2016-08-10T23:09:26+00:00

When a build fails, it shouldn't have links on its build time in the recent builds area or in the all builds table. [YOCTO #8443] (Bitbake rev: 3d7b247512eb01607741f5f6ce7cb01d241e49e7) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster: move most recent builds templating to client

2016-08-10T23:09:26+00:00

The most recent builds area of the all builds and project builds table needs to update as a build progresses. It also needs additional functionality to show other states (e.g. recipe parsing, queued) which again needs to update on the client side. Rather than add to the existing mix of server-side templating with client-side DOM updating, translate all of the server-side templates to client-side ones (jsrender), and add logic which updates the most recent builds area as the state of a build changes. Add a JSON API for mostrecentbuilds, which returns the state of all "recent" builds. Fetch this via Ajax from the build dashboard (rather than fetching the ad hoc API as in the previous version). Then, as new states for builds are fetched via Ajax, determine whether the build state has changed completely, or whether the progress has just updated. If the state completely changed, re-render the template on the client side for that build. If only the progress changed, just update the progress bar. (NB this fixes the task progress bar so it works for the project builds and all builds pages.) In cases where the builds table needs to update as the result of a build finishing, reload the whole page. This work highlighted a variety of other issues, such as build requests not being able to change state as necessary. This was one part of the cause of the "cancelling build..." state being fragile and disappearing entirely when the page refreshed. The cancelling state now persists between page reloads, as the logic for determining whether a build is cancelling is now on the Build object itself. Note that jsrender is redistributed as part of Toaster, so a note was added to LICENSE to that effect. [YOCTO #9631] (Bitbake rev: c868ea036aa34b387a72ec5116a66b2cd863995b) Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster: tests test_new_project_page Catch button not enabled exception

2016-08-10T23:07:09+00:00

When using firefox and selenium we get an exception generated when a disabled button click is attempted. This should happen in the test but we need to catch the exception to make sure it doesn't cause the test to fail. [YOCTO #10056] (Bitbake rev: 06f74fe91f8e162f49a4e856a62a97093b48262a) Signed-off-by: Michael Wood Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie