Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:Summer 2019 Sprint 10, Summer 2019 Sprint 11, Fall 2019 Sprint 3, Fall 4 : 30 Sep to 11 Oct
Description
We now have working App Stores available on various "dev" appstore testing sites hosted on AWS ECs.
Now, we need to try out the full App workflow cycle and make sure it is working as expected:
- Select a test App Store site with up-to-date code
- Select an App (can use Super Simple IGB App as a test case)
- Submit App to App Store
- Add "pending_releases" App Store repository to your local IGB for testing
- Confirm you can install and run the "pending" App in your IGB
- Get your App released - by an Admin user
- Observe that your App is added to the released Apps in App Store
- Now confirm that if you add "released" apps repository to your IGB, you can now see and install your App from App Store
- Edit the App page for your App – add publication, add logo, add tags (categories), add authors
- Develop an updated version of your App - increment the version by editing its POM
- Confirm that you can upload a new version of your App without needing to get it approved
- Confirm you can update the App
Run the above workflow and take notes on issues you encounter. This includes usability as well as functional issues – make note of anything that you found confusing or unexpected.
Attachments
Issue Links
- relates to
-
IGBF-1865 Continue to improve IGB App Store UI and functionality
-
- Closed
-
-
IGBF-1894 Apps are not installing via Appstore in IGB
-
- Closed
-
-
IGBF-1895 Display the developer guidelines on OSGi bundles before the files get selected and perform checks before submitting the app.
-
- Closed
-
-
IGBF-1896 Upload the apps with symbolic name to the s3 bucket
-
- Closed
-
-
IGBF-1897 Fix Appstore confirmation email content related issues
-
- Closed
-
-
IGBF-1898 Add email popup related issues - close button and error message
-
- Closed
-
-
IGBF-1899 IGB not running message displayed in AppStore even if IGB is running
-
- Closed
-
-
IGBF-1900 Bundle description should be optional while submitting an app in AppStore
-
- Closed
-
-
IGBF-1901 Check and fix AppStore css/formatting issues on all major browsers
-
- Closed
-
-
IGBF-1917 Minor Bug Fixes
-
- Closed
-
-
IGBF-2064 Design better workflow following submitting a new release
-
- Closed
-
-
REL-32 Test Appstore Workflow
-
- Testing To-Do
-
-
IGBF-1885 Fix App Page for Citation and Resource
-
- Closed
-
-
IGBF-1887 Dismiss Star Rating Alert
-
- Closed
-
-
IGBF-1890 Change Link to support Https in Approve App Mail
-
- Closed
-
-
IGBF-1891 Add Popover to the Screenshot Images
-
- Closed
-
I am currently trying out the new App Store and I noticed the following issues/suggestions:
1. I tried installing apps after downloading them from bitbucket. They were not working in the app-store as some dependencies were missing. I expected that since the apps are developed specifically for IGB, the jar should work without any further modification. This observation is valid only for 23andme and ProtAnnot app. (Command Socket, Merge Annotation and Geometric mean operator worked seamlessly.)
2. After I selected the app in the file chooser, I was seeing the information about OSGi bundles. After I submitted the app, the validation steps were performed on the jar. It would have been nicer if the information about OSGi bundles was shown upfront and the validation checks were performed right after the jar selection and before the user hit the submit button. This will also prevent the developer from submitting the app multiple times.
3. After I submitted ProtAnnot app, I received a mail about pending app approval. However, the app was uploaded in the S3 bucket but with a different name than expected, therefore the app was not installing.
(This could be happening because the app name and presentation name of ProtAnnot were different. We need to fix this and consider only one name while generating the repository.xml if that is the case.)
3a. Enhancement suggestion: The Email subject is generic: "IGB App Store - Submission Done!". We could make it more informative by adding the name of the submitted app in the email, something like this: "IGB App Store - ProtAnnot Submission Done!"
4. After I approved the app as admin, I received the approval mail. However the link in the mail http://testappstore.bioviz.org:443/apps/protannot is Http and not Https, so it did not work.
Also, the link looks odd with the 443 port included in the Http link.
5. In editing options of the app, I was unable to add more email addresses of editors. Got the error saying "Email is invalid.". I was also not able to close the "add email" pop-up.
6. After submit app, confirm submission page is displayed. But as per present behavior, the initial submit button triggers the email and goes ahead and submits the app, without waiting for developer confirmation/cancellation. This needs to be fixed.
7. While editing the rating of the app, it opens a pop-up saying "Thank you for your input, the rating has been updated." After showing the message the pop-up should get automatically closed. If the user clicks on the ratings multiple times, multiple popups are displayed and main content of the page shifts down and is inaccessible after one point as there is no right scrollbar in the page.
8. I closed IGB to verify if I was getting alert "IGB is not running". I got the alert, but I continued to get that alert even after IGB was running again.
9. After adding details to the app like website, tutorial, and code repository, email, it is not displaying correctly on the view app page.
10. Currently if we click on screenshots they get opened in a new window. I suggest they should open as a pop-up on the same page and should rotate with left and right arrow button. On escape the image popup should get closed.