meta-iotqa: add qa tests for flatpak.

[shashwatpandey221091]

Add tests for flatpak python interface.

Signed-off-by: Shashwat Pandey [email protected]

[shashwatpandey221091]

Please help to test this build.

[refkit-ci]

Can one of the admins verify this patch?

[okartau]

ok to test

[okartau]

I noticed there is proxy value set, which may be good in development context, but may be sub-optimal in CI system

[shashwatpandey221091]

Noted. For now the concerned script is disabled due the external network dependency.

Will remove the proxy value set from the CI system. Thanks for the input.

[epyeoh]

Hi SP,
2 comments:

1. I noticed the commit message is "Add tests for flatpak python interface.", but I noticed that you are mainly testing flatpak commandline, right?
2. Both test_flatpak_list.py and test_flatpak_version.py are executing single commandline, will it be possible to get rid of the python script with direct execution of in the unit test itself?

[shashwatpandey221091]

Hi Peng,

1. Yes, for listing and checking version of flatpak, just using the command line. Though for installation and running application, performing some python operation. But since both test_flatpak_install.py and test_flatpak_runapp.py scripts are disabled for now, it's basically testing flatpak using command line.

2. It's a good suggestion of including the command line in the unit test itself instead of calling python script. Will update the unit test accordingly.

Thanks.

[shashwatpandey221091]

Updated as per Peng's suggestions. Please test.

[shashwatpandey221091]

Please remove the test build label and review the pull request. Also merge it to the master branch if looks ok.

Thanks.

[epyeoh]

@klihub please help to review this flatpak test cases.

[klihub]

@epyeoh These test cases are ok as such, but they look very basic to me: list installed flatpaks (without checking the output) and run a known flatpak application (without checking its output or anything else).

Have you taken a look at what Patrick has done for ostree ? If you'd write similar test cases then I'd expect to have a some test set like:

• basic test for installing and application (check list of apps prior to installation, check that new app show up after the installation)
• basic test for removing the installed application (check list of apps prior to installation, check that the removed app disappear after removal)
• basic test for updating an application (have a known flatpak app which print something known and exit, create and export an new version which prints something else, check that after the update it prints the new string)

Have you considered something along those lines ?

[epyeoh]

@klihub Yes, current test case is basic tests for flatpak.
Our initial plan is to:

1. First, develop basic tests (which is current set of tests), then
2. Develop advance tests following Patrick ostree tests
   We hope that this set of basic tests will be able to complete first.