History

Jonathan Rainville e0172c8bb9 chore: add mayfail to tests that fail on CI		2023-02-09 11:08:10 +01:00
..
doc	test(chore): Renamed and reorganized files and added files flow diagram	2022-11-22 12:44:57 +01:00
fixtures	test(community): add a test where the admin can delete a user's message	2023-01-04 11:12:47 -05:00
src	test(community): re-add mark as read test in community tests	2023-02-08 13:46:15 -05:00
testSuites	chore: add mayfail to tests that fail on CI	2023-02-09 11:08:10 +01:00
.gitignore	test(settings/profile): test bio and social links	2022-08-17 13:18:32 +02:00
README.md	test(doc): Added info about Squish versions tested	2023-02-08 16:19:52 -05:00

README.md

status-desktop-ui-test

UI test application for Status Desktop

Test automation project that uses Squish as a testing tool with BDD.
Information about its architecture can be found in wiki.

Preparing the environment to develop and run tests

Install Squish and run its IDE.
File / Open Test Suite and browse to testSuites directory.
Once the suite is open, click Test Suite Settings button to configure the AUT (Application Under test).
- Select AUT tab and browse until the corresponding status-desktop\bin\nim_status_client binary is set.
- Uncheck Automatically start the AUT option (if it is already checked).
- Save changes.

Now you should be able to create new suites, test cases and run the existing ones just only by clicking Run buttons!!

Here a more detailed installation guide specific for this project.

Squish versions tested

Status APP Qt version	Squish version	Squish Qt version	Local macOS Monterey 12.3.1	CI
5.14.2	6.7.2	5.14	OK	OK
5.15.2	6.7.2	5.14	OK	OK
5.15.2	7.0.1	5.15	KO	KO
5.15.2	7.1.0	5.14	KO	KO
5.15.2	7.1.0	5.15	KO	KO

NOTE: KO means the test execution hangs on squish.waitForObject() or squish.findObject(). Seen this behaviour particularly in Onboarding / Create Password Screen.

Last status app tested: Master branch - Commit: 5f4000b7a57cd5c268c3ebf847e2b3ef1a8ff96a