Repository navigation
feat: (teams) - #18040
feat: (teams)#18040alperozturk96 wants to merge 26 commits into
Conversation
20d1b77 to
7a5fb7f
Compare
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
53e11c8 to
0535727
Compare
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
|
test-Unit test failed, but no output was generated. Maybe a preliminary stage failed. |
|
stable22-IT test failed, but no output was generated. Maybe a preliminary stage failed. |
|
stable35-IT test failed, but no output was generated. Maybe a preliminary stage failed. |
|
master-IT test failed, but no output was generated. Maybe a preliminary stage failed. |
|
Hi 👋 @alperozturk96 (cc: @tobiasKaminsky, @nimishavijay ) I found the scope of this PR super interesting to cover from a user journey perspective, so I created a dedicated Job for it and wanted to share where things stand. I describe user journeys as User Journey Graphs (UJG), and journey-mesh executes them. It builds the APK from this PR (with android-library#2209) and starts Nextcloud 35.0.2 in Docker. It then drives one emulator per person, checking each step on screen and each effect on the server. Scenario: Alice creates a team, requires invitations to be accepted, and invites Bob. Bob accepts the invitation and opens the team folder. Test-side adjustments: The server's "unsupported browser" page is disabled (the emulator's WebView is version 124), and Appium's
Report (local run, same results) · Github CI log If I've missed anything about how the scenario is supposed to work, please ping me. Happy to adjust it! Long live open source! 🚀 |
Other PRs
Library PR: nextcloud/android-library#2209
Changes
Out of scope
Screenshots