Also we have started testing earlier enough I guess. Pavithra started testing the previous packs in last August/Spetember. And this round of testing started in January. The problem was some features were not ready and features changed through out last couple of months, which invalidates the tests we did and have to do it again.
On Tue, Apr 7, 2015 at 1:49 PM, Nirodha Pramod <niro...@wso2.com> wrote: > Hi, > > Our concerns were that we had the above mentioned L1s and L2s and added > new features in the latest packs, which makes it not ready to be released > in two more days. And we have been getting packs like every other day(some > with config changes too) so it is a bit hard to manage testing on all the > given packs. So to do a decent release we would need more time to test. > Since we were running low on headcount we could not allocate more than one > in past few weeks. However we have allocated another person to help with > AppM testing. > > Thanks, > Nirodha > > On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe <sume...@wso2.com> > wrote: > >> Shakar, >> All these are available on packs. >> >> Problems >> - we now have 8 L1s, 26 L2s >> - QA was running low on resources, so only one engineer was available for >> last 2+ weeks >> - So QA wants to test more >> >> >> On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar < >> shan...@wso2.com> wrote: >> >>> Hi Sumedha, >>> >>> Yes, thats all fine. I am asking when we will get the pack with all >>> these features/ changes done. Meaning the proper alpha with features >>> frozen. If we still don't know that date, it is also fine, but we can plan >>> the QA based on that. >>> >>> On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe <sume...@wso2.com> >>> wrote: >>> >>>> On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar < >>>> shan...@wso2.com> wrote: >>>> >>>>> Hi Sumedha, Dinusha, >>>>> >>>>> When do we have the alpha release with feature frozen? >>>>> >>>> >>>> Hi Shankar, >>>> We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ >>>> lists out all public packs we have hosted). >>>> >>>> Then Isabelle & Chris used this alpha pack to do a series of partner >>>> briefings. >>>> >>>> After these briefings we got feedback to improve following areas: >>>> 1. App Publishing flow is too lengthy for a newbie >>>> 2. App Policy Mgt should be separated out from App Publishing (thread: >>>> [APPM] [IS] Change of XACML based authorization) >>>> 3. Make graphs more aesthetic >>>> 4. Improve first timers experience better by adding a sample app >>>> deployer (thread: dev: App Manager sample deployer) >>>> >>>> We also discovered following: >>>> - We only support EMM 1.0. So need to add support for both EMM 1.0.0 & >>>> MDM 2.0.0 ("thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App >>>> Management feature to App Manager) >>>> >>>> - ES only supports permission check for login only. So we had to >>>> implement permission model on top of ES (thread : Life Cycles >>>> transition for Apps in APPM) >>>> >>>> Apart from this RuwanA finished his project on App Discovery (thread: >>>> [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) >>>> >>>> >>>> So after the alpha on 23rd of December, above are the changes we >>>> introduced apart from fixing issues reported. >>>> >>>> >>>> >>>> >>>>> On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake <yasas...@wso2.com >>>>> > wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> This is to update the Latest progress on App Manager Release testing. >>>>>> Currently there are following blockers and critical issues. IMHO these >>>>>> need >>>>>> to be fixed before the release. >>>>>> >>>>>> - Oracle DB script related issues. >>>>>> - BAM toolbox issues/ Stats related issues >>>>>> - Single Logout >>>>>> - BPS integration issues. (Was Fixed with the latest pack (5th >>>>>> April Pack), yet to verify the fix) >>>>>> - Session Related issues. etc. >>>>>> >>>>>> Some of these issues are listed from [1] - [9]. In total(Open, >>>>>> Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues >>>>>> and 15 L4 & L5 issues. >>>>>> >>>>>> Along the way we faced several challenges when testing APP-M apart >>>>>> from the blocking issues we faced, following new features were added >>>>>> >>>>>> - App Discovery >>>>>> - New Stats pages >>>>>> - Sample Deploying feature >>>>>> >>>>>> Some features also got changed >>>>>> >>>>>> - EMM integration >>>>>> - XACML policy UI etc. >>>>>> >>>>>> There were some configuration level changes in web-apps as well as in >>>>>> app-manager.xml/ user-mgt.xml which affected the Automation process. Lack >>>>>> of documentation was another issue we faced. >>>>>> >>>>>> Currently we are in the process of testing untested areas and bug >>>>>> fixed scenarios. Due to above mentioned issues IMHO I highly doubt >>>>>> whether >>>>>> we can do a proper round of testing before the planned release date. >>>>>> >>>>>> [1] - https://wso2.org/jira/browse/APPM-718 >>>>>> [2] - https://wso2.org/jira/browse/APPM-715 >>>>>> [3] - https://wso2.org/jira/browse/APPM-686 >>>>>> [4] - https://wso2.org/jira/browse/APPM-651 >>>>>> [5] - https://wso2.org/jira/browse/APPM-481 >>>>>> [6] - https://wso2.org/jira/browse/APPM-324 >>>>>> [7] - https://wso2.org/jira/browse/APPM-511 >>>>>> [8] - https://wso2.org/jira/browse/APPM-544 >>>>>> [9] - https://wso2.org/jira/browse/APPM-639 >>>>>> >>>>>> With Regards, >>>>>> >>>>>> >>>>>> On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka <dinu...@wso2.com >>>>>> > wrote: >>>>>> >>>>>>> Hi Yasassri, >>>>>>> >>>>>>> Please find the latest pack in [1]. We could find root cause for >>>>>>> some of the intermittent issues that you have reported. But we included >>>>>>> some debug logs to possible places, so that we can narrow down the >>>>>>> issue if >>>>>>> it appeared on latest pack too. Please enable jaggery debug logs before >>>>>>> you >>>>>>> start testing the pack. >>>>>>> >>>>>>> [1]. http://builder1.us1.wso2.org/~appm/19-03-2015/ >>>>>>> >>>>>>> Regards, >>>>>>> Dinusha. >>>>>>> >>>>>>> On Tue, Mar 17, 2015 at 6:39 PM, Yasassri Ratnayake < >>>>>>> yasas...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> Meeting Notes >>>>>>>> >>>>>>>> - AM team will try to fix all the issues related to instability >>>>>>>> and share a new pack tomorrow. >>>>>>>> - Testing on oracle will be done based on the time available >>>>>>>> before the expected release date. >>>>>>>> - Long running test has to be run by the QA team. (on a >>>>>>>> standalone setup) >>>>>>>> - All features and UI's are currently finalized and no major >>>>>>>> changes will happen. >>>>>>>> >>>>>>>> With Regards, >>>>>>>> >>>>>>>> On Tue, Mar 17, 2015 at 6:14 PM, Yasassri Ratnayake < >>>>>>>> yasas...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi Dinusha, >>>>>>>>> >>>>>>>>> Sorry for the ambiguity in the mail. Please see my comments in-line >>>>>>>>> >>>>>>>>> >>>>>>>>>>> Hi All, >>>>>>>>>>> >>>>>>>>>>> This is to update the current status of the App Manger release >>>>>>>>>>> cycle. >>>>>>>>>>> >>>>>>>>>>> We had issues initially when testing due to following reasons >>>>>>>>>>> >>>>>>>>>>> - There was no decided permission model embedded to AM. >>>>>>>>>>> >>>>>>>>>>> This is finalized and we are not going to change the model ! >>>>>>>>>> There is a mail thread for this even ! >>>>>>>>>> >>>>>>>>> >>>>>>>>> This is an issue we had before March 6th pack, As mentioned the >>>>>>>>> permission model is finalized ATM. >>>>>>>>> >>>>>>>>> >>>>>>>>>>> - UI got changed along the way >>>>>>>>>>> >>>>>>>>>>> There were some usability improvements done after reviewing >>>>>>>>>> with UX team. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> - Features were not finalized. >>>>>>>>>>> >>>>>>>>>>> What you mean by features are not finalized ? >>>>>>>>>> >>>>>>>>> >>>>>>>>> Along the way there were some new features added, these were >>>>>>>>> issues we faced initially when we started testing. >>>>>>>>> >>>>>>>>> 1. Allow annonymous access >>>>>>>>> 2. Skip Creating Proxying WebApp >>>>>>>>> 3. New Dashboard was added to add Policies etc. >>>>>>>>> 4. Policy groups >>>>>>>>> 5. New statistical graphs/options, completely reverted statistics >>>>>>>>> page >>>>>>>>> 6. Notification on App Rejection etc. >>>>>>>>> >>>>>>>>> Now, I believe all the features are finalized. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> *Current Status* >>>>>>>>>>> >>>>>>>>>>> ATM the latest pack is unstable so we are not testing the pack >>>>>>>>>>> in the clustered setup, hence we are doing our tests in a >>>>>>>>>>> standalone setup. >>>>>>>>>>> And still the workflow process is not finalized. >>>>>>>>>>> >>>>>>>>>> AFAIK, there is a tenant specific issue relate to life-cycle >>>>>>>>>> loading. But, even with that we can continue super tenant scenarios >>>>>>>>>> in a >>>>>>>>>> cluster environment. Workflow process is not finalized ??? >>>>>>>>>> >>>>>>>>> >>>>>>>>> I'm claiming the instability based on these observation, irregular >>>>>>>>> behavior in some functions, Exceptions thrown intermittently, I have >>>>>>>>> reported most of them. [1] - [7]. These are all intermittent >>>>>>>>> exceptions >>>>>>>>> that I observe when going through the general flow. The stability has >>>>>>>>> improved lot in the later packs, but there are some glitches which >>>>>>>>> needs to >>>>>>>>> be investigated further. >>>>>>>>> >>>>>>>>> I have raised concerns regarding the workflow issue in the thread >>>>>>>>> "[APP-M] >>>>>>>>> Workflows in App Manager". >>>>>>>>> >>>>>>>>> [1] - https://wso2.org/jira/browse/APPM-545 >>>>>>>>> [2] - https://wso2.org/jira/browse/APPM-554 >>>>>>>>> [3] - https://wso2.org/jira/browse/APPM-563 >>>>>>>>> [4] - https://wso2.org/jira/browse/APPM-491 >>>>>>>>> [5] - https://wso2.org/jira/browse/APPM-490 >>>>>>>>> [6] - https://wso2.org/jira/browse/APPM-439 >>>>>>>>> [7] - https://wso2.org/jira/browse/APPM-324 >>>>>>>>> >>>>>>>>> With Regards >>>>>>>>> -- >>>>>>>>> Yasassri Ratnayake >>>>>>>>> Software Engineer - QA >>>>>>>>> WSO2 Inc ; http://wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> *Mobile : +94715933168 <%2B94715933168>* >>>>>>>>> *Blog : http://yasassriratnayake.blogspot.com/ >>>>>>>>> <http://yasassriratnayake.blogspot.com/>* >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Yasassri Ratnayake >>>>>>>> Software Engineer - QA >>>>>>>> WSO2 Inc ; http://wso2.com >>>>>>>> lean.enterprise.middleware >>>>>>>> *Mobile : +94715933168 <%2B94715933168>* >>>>>>>> *Blog : http://yasassriratnayake.blogspot.com/ >>>>>>>> <http://yasassriratnayake.blogspot.com/>* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Dinusha Dilrukshi >>>>>>> Senior Software Engineer >>>>>>> WSO2 Inc.: http://wso2.com/ >>>>>>> Mobile: +94725255071 >>>>>>> Blog: http://dinushasblog.blogspot.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Yasassri Ratnayake >>>>>> Software Engineer - QA >>>>>> WSO2 Inc ; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> *Mobile : +94715933168 <%2B94715933168>* >>>>>> *Blog : http://yasassriratnayake.blogspot.com/ >>>>>> <http://yasassriratnayake.blogspot.com/>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> S.Uthaiyashankar >>>>> VP Engineering >>>>> WSO2 Inc. >>>>> http://wso2.com/ - "lean . enterprise . middleware" >>>>> >>>>> Phone: +94 714897591 >>>>> >>>> >>>> >>>> >>>> -- >>>> /sumedha >>>> m: +94 773017743 >>>> b : bit.ly/sumedha >>>> >>> >>> >>> >>> -- >>> S.Uthaiyashankar >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com/ - "lean . enterprise . middleware" >>> >>> Phone: +94 714897591 >>> >> >> >> >> -- >> /sumedha >> m: +94 773017743 >> b : bit.ly/sumedha >> > > > > -- > > *Nirodha Gallage* > Senior Software Engineer, QA. > WSO2 Inc.: http://wso2.com/ > Mobile: +94716429078 > -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
