Skip to content
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

Add sfdk init tests #17

Merged
merged 1 commit into from Feb 13, 2023
Merged

Add sfdk init tests #17

merged 1 commit into from Feb 13, 2023

Conversation

vigejolla
Copy link
Member

Adding tests so that we can catch these kind of issues automatically in the future

Comment on lines 55 to 32
Template Init
[Template] Build Initialized Project
qtquick2app qmake ${DEVICE.arch}
qtquick2app cmake ${DEVICE.arch}
qtquick2app-qmlonly qmake noarch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also test build phase separation and shadow builds with cmake etc. So I would rather turn the existing test cases to templates and test those with all combinations of templates and builders. I would use the "Template" suffix to name the templates:

Basic Build
    [Template]    Basic Build Template
    ...

Basic Build (Shadow)
    [Template]    Basic Build (Shadow) Template
    ...
...
*** Keywords ***
...
Basic Build Template
    [Arguments] ...
    [Setup] ...
    ....
    [Teardown] ...
...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I can do that.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Note: For some reason robot does now allow [Setup] in a template - but luckily it's possible to just use the setup keyword directly.

Test both qmake and cmake and also qmlonly

Signed-off-by: Ville Nummela <ville.nummela@jolla.com>
@vigejolla vigejolla merged commit b3dcb82 into master Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants