Task #8567 (closed)
Opened 12 years ago
Closed 12 years ago
Additional changes to the gateway tests
| Reported by: | atarkowska | Owned by: | cneves |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-4.4.4 |
| Component: | OmeroPy | Version: | n.a. |
| Keywords: | n.a. | Cc: | web-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Static set of roles:
- anonymous, a user that can see only world readable data (which is
emulated by having the user be member of the read-only group)
- author, user that owns data in the journal, can edit it while group
is RW.
- editor, a system user
We use one group for each project and all objects linked to it
recursively, owned by author.
So the tests that I would envision here are:
- (rw--) create objects as author in new group, edit as author, edit as
editor, can't edit as anonymous
- read as editor, read as author, can't read as anonymous
- (r---) (once we have) chmod the group to read only, can't edit as
author, edit as editor, can't edit as anonymous
- read as editor, read as author, can't read as anonymous
- (r-r-) (once we can) make the group world readable, can't edit as
author, edit as editor, can't edit as anonymous
- read as editor, read as author, read as anonymous
- remove world read, retest (r---)
- add group write, retest (rw--)
This covers the basic multi user / multi group interactions I need.
There are deeper things to be handled (like single rdefs per image
regardless of user) but these are better handled in the journal specific
code and tested there too.
Change History (12)
comment:1 Changed 12 years ago by jburel
- Sprint changed from 2012-05-08 (14) to 2012-05-22 (15)
comment:2 Changed 12 years ago by atarkowska
- Summary changed from Additional changes to the gateway to Additional changes to the gateway tests
comment:3 Changed 12 years ago by jburel
- Sprint changed from 2012-05-22 (15) to 2012-06-05 (16)
Moved from sprint 2012-05-22 (15)
comment:4 Changed 12 years ago by jburel
- Sprint changed from 2012-06-05 (16) to 2012-06-19 (17)
Moved from sprint 2012-06-05 (16)
comment:5 Changed 12 years ago by jburel
No owner for that one, and in the sprint, who is working on it?
comment:6 Changed 12 years ago by jburel
- Sprint changed from 2012-06-19 (17) to 2012-07-03 (18)
Moved from sprint 2012-06-19 (17)
comment:7 Changed 12 years ago by jburel
- Sprint changed from 2012-07-03 (18) to 2012-07-17 (19)
Moved from sprint 2012-07-03 (18)
comment:8 Changed 12 years ago by jmoore
- Owner set to cneves-x
Carlos, passing to you since you said you've been working on tests. Have you covered any of these cases? If not, should we just push?
comment:9 Changed 12 years ago by cneves
Many of these tests are in the commercial side. I am adding more tests and improving coverage on the open source side as time permits so this ticket is certainly for me, but I can't commit to a specific timeframe yet.
comment:10 Changed 12 years ago by jmoore
- Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.4.1
- Sprint 2012-07-17 (19) deleted
Ok. Then moving to 4.4.1. Maybe there's some chance of back-porting (side-porting) a large block of them over the summer.
comment:11 Changed 12 years ago by jmoore
Carlos, can this be closed now with https://github.com/openmicroscopy/openmicroscopy/pull/324 or is there something more?
comment:12 Changed 12 years ago by cneves
- Resolution set to fixed
- Status changed from new to closed
There are many improvements on the PR Josh mentioned, and most of what is described is being tested now. While there might be corner cases not tested atm, I'm closing this ticket as it has grown stale.
Moved from sprint 2012-05-08 (14)