Hi Ivan, Thanks for your advice.
I agree with the general idea of automating regression test for the UI, however, I don't have the expertise around writing tests using best practices, and I look forward to you or anyone else who can share some pointers, examples or maybe a plan. Given the UI is largely config and data driven, the number of components shouldn't be high except for any customization we do for some views. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com ________________________________ From: Ivan Kudryavtsev <kudryavtsev...@bw-sw.com> Sent: Wednesday, October 9, 2019 09:37 To: dev <dev@cloudstack.apache.org> Subject: Re: [VOTE] Primate as modern UI for CloudStack Hello, community. I know it's just a voting process, but still... a piece of wisdom from webdev company: 1. Manual testing is an extremely bad idea, you've meet a lot of regression, much more than the backend typically has. 2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1, without UI automation QA engineers, so 3/1 is average ratio for real life high quality web UIs. 3. Try to use/invent some sort of Django-like UI generator frameworks, no code manually. I see the high risk of fail without that. May be need to add some sort of metadata to backend first. The Cloudmonkey approach is a great basic idea... Oracle also has certain frameworks for that. Ideally, to define the forms and sitemap and generate everything else from the ORM. 4. Happy to see the initiative, as it could help to decrease the pace of backend changes and increase the stability, as certain amount of influencers turn into frontend JS developers. ср, 9 окт. 2019 г., 7:45 Anurag Awasthi <anurag.awas...@shapeblue.com>: > +1 > > Kind Regards, > Anurag Awasthi > ________________________________ > From: Marco Sinhoreli <marco.sinhor...@shapeblue.com> > Sent: Wednesday, October 9, 2019 4:10 AM > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org>; > us...@cloudstack.apache.org <us...@cloudstack.apache.org>; > priv...@cloudstack.apache.org <priv...@cloudstack.apache.org> > Subject: Re: [VOTE] Primate as modern UI for CloudStack > > +1 > > > Marco Sinhoreli > Latam Technical Director > marco.sinhor...@shapeblue.com > mobile: +55 11 95656-3636 > > Rua Gomes de Carvalho, 911 – Sala 316 > Vila Olímpia, São Paulo, SP, Brasil, 04547-003 > Phone: + 55 11 2818-3419 > http://www.shapeblue.com/ | twitter: @shapeblue > > Em 07/10/2019 08:31, "Rohit Yadav" <rohit.ya...@shapeblue.com> escreveu: > > All, > > The feedback and response has been positive on the proposal to use > Primate as the modern UI for CloudStack [1] [2]. Thank you all. > > I'm starting this vote (to): > > * Accept Primate codebase [3] as a project under Apache CloudStack > project > * Create and host a new repository (cloudstack-primate) and follow > Github based development workflow (issues, pull requests etc) as we do with > CloudStack > * Given this is a new project, to encourage cadence until its > feature completeness the merge criteria is proposed as: > * Manual testing against each PR and/or with screenshots from > the author or testing contributor, integration with Travis is possible once > we get JS/UI tests > * At least 1 LGTM from any of the active contributors, we'll > move this to 2 LGTMs when the codebase reaches feature parity wrt the > existing/old CloudStack UI > * Squash and merge PRs > * Accept the proposed timeline [1][2] (subject to achievement of > goals wrt Primate technical release and GA) > * the first technical preview targetted with the winter 2019 > LTS release (~Q1 2020) and release to serve a deprecation notice wrt the > older UI > * define a release approach before winter LTS > * stop taking feature FRs for old/existing UI after winter 2019 > LTS release, work on upgrade path/documentation from old UI to Primate > * the first Primate GA targetted wrt summer LTS 2020 (~H2 > 2019), but still ship old UI with a final deprecation notice > * old UI codebase removed from codebase in winter 2020 LTS > release > > The vote will be up for the next two weeks to give enough time for PMC > and the community to gather consensus and still have room for questions, > feedback and discussions. The results to be shared on/after 21th October > 2019. > > For sanity in tallying the vote, can PMC members please be sure to > indicate "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > [1] Primate Proposal: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI > > [2] Email thread reference: > https://markmail.org/message/z6fuvw4regig7aqb > > [3] Primate repo current location: > https://github.com/shapeblue/primate > > > Regards, > > Rohit Yadav > > Software Architect, ShapeBlue > > https://www.shapeblue.com > > rohit.ya...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > > > anurag.awas...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > rohit.ya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
