xpra icon
Bug tracker and wiki

Opened 3 months ago

Last modified 2 months ago

#2231 new enhancement

automated tests should be able to test html5 client

Reported by: Antoine Martin Owned by: Jonathan Anthony
Priority: critical Milestone: 3.0
Component: tests Version: 2.5.x
Keywords: Cc:

Description

And record the client type so we can compare python vs html5.

Change History (3)

comment:1 Changed 3 months ago by Antoine Martin

Priority: majorcritical
Status: newassigned

Blocker for #2232.

comment:2 Changed 3 months ago by Antoine Martin

Blocked by #2251

comment:3 Changed 2 months ago by Antoine Martin

Owner: changed from Antoine Martin to Jonathan Anthony
Status: assignednew

Working OK now that #2251 is fixed + minor fixes from r22517.

With one important caveat: the browser session must not be resumed from an earlier one as this would interfere with the testing, so one has to use a profile specifically setup for this testing.
Either a brand new user, or forcing a new profile:

  • firefox now uses firefox -P Test: so you must create a "Test" profile
  • google-chrome now uses google-chrome --user-data-dir=~/Downloads/TEMP, so you must run mkdir -p ~/Downloads/TEMP once.

Notes:

  • more browsers could be added, @encodedEntropy: do you have a standalone one I could use for testing?
  • we could also add a setting for testing via https vs http, but again this would require manual steps for accepting the certificates - probably not worth the hassle.
  • when running the tests with a browser as client, it doesn't make sense to have XPRA_TEST_ENCODINGS and many of the other options, so r shortcuts that out. Which means that there are fewer browser tests than python client tests sets. Adjust the test options accordingly.
  • do we also want to set the window size so that the test setup is more reproducible? Firefox has an option, google-chrome does not. (so it would require an xdotool hack)
  • I have seen firefox occasionally failing to startup and getting an error page instead of the html5 client - not sure why that is yet. It means the corresponding test data is garbage.. Another time, it came up with a "do you want to refresh" dialog... PITA

@encodedEntropy: I think there's enough there to hand over to you, let's get some data and iterate.

Note: See TracTickets for help on using tickets.