Skip to content

Added testcases about adding and removing users to groups using subad…#25809

Merged
PVince81 merged 4 commits into
masterfrom
integration-tests-subadmins
Aug 22, 2016
Merged

Added testcases about adding and removing users to groups using subad…#25809
PVince81 merged 4 commits into
masterfrom
integration-tests-subadmins

Conversation

@SergioBertolinSG

Copy link
Copy Markdown
Contributor

…mins

please review @PVince81

@SergioBertolinSG SergioBertolinSG added this to the 9.2 milestone Aug 16, 2016
@mention-bot

Copy link
Copy Markdown

@SergioBertolinSG, thanks for your PR! By analyzing the annotation information on this pull request, we identified @PVince81, @LukasReschke and @DeepDiver1975 to be potential reviewers

And user "subadmin" exists
And user "brand-new-user" exists
And group "new-group" exists
And Assure user "subadmin" is subadmin of group "new-group"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

not sure why we need the word "Assure" here as all commands we give here are about assuring 😄

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Well, that is because there are two situations, one where you just want to check something, like in when statements and one when you want to check it and modify something to make it be that way.

@PVince81

Copy link
Copy Markdown
Contributor

Looks good, thanks a lot! 👍

@SergioBertolinSG

SergioBertolinSG commented Aug 16, 2016

Copy link
Copy Markdown
Contributor Author

@PVince81 After reading your review I've realized I was adding users to groups in the final then statements. I think we should differenciate assure and check functions in every step to have it clear. 'Assure' checks and makes a modification, good for given statements and 'Check' only checks the current status, good for then statements.

I understand it is a bit confusing at the moment as we don't have it explicit in every statement.

@PVince81

Copy link
Copy Markdown
Contributor

@DeepDiver1975 if only OCI fails, does it mean the integration tests at least passed ? Or is there a risk that they didn't ? (I don't want to read the full log)

We might want to increate the OCI timeout, or even more OCI to a separate job to avoid confusion and make it easier to ignore.

@SergioBertolinSG

Copy link
Copy Markdown
Contributor Author

Perhaps adding a job only running integration tests? It was useful before.

@PVince81

Copy link
Copy Markdown
Contributor

@SergioBertolinSG the new tests, (or the new Jenkins server?) at some point, should output a results matrix even from a single execution.

@DeepDiver1975

Copy link
Copy Markdown
Member

Job execution is sequential. Click on the pr on Jenkins and you will get an overview over all Jobs which got executed ob this pr.

@DeepDiver1975

Copy link
Copy Markdown
Member

Looks like the Oracle Docker did not Start within 2h

00:16:45.552 Fire up the oracle docker
02:16:43.691 Sending interrupt signal to process

@PVince81

Copy link
Copy Markdown
Contributor

Click on the pr on Jenkins

Ah! That's the page I was looking for. Basically open the log URL and remove the suffix: https://jenkins.owncloud.org/job/owncloud-core/job/core/job/PR-25809

@PVince81 PVince81 merged commit 849eb3c into master Aug 22, 2016
@PVince81 PVince81 deleted the integration-tests-subadmins branch August 22, 2016 15:33
@lock

lock Bot commented Aug 4, 2019

Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock Bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants