> On Feb 2, 2017, at 10:46 AM, Jamo Luhrsen <jluhr...@gmail.com> wrote: > > > > On 02/02/2017 10:38 AM, Luis Gomez wrote: >> So I see 3 actions from integration today’s call: >> >> 1) Find out what documentation is relevant for test end users (e.g. >> developers, integration people). This may include: >> >> - Feature/functionality description. >> - High level test plan. >> - Detailed test cases description. >> >> 2) Look at what of the above can be automatically generated from the robot >> test itself, either using robot parsing scripts or creating our own. Note: >> we can use doc hackathon for this. > > https://trello.com/c/u1Sri2d9/441-int-test-autocreate-robot-testdoc > <https://trello.com/c/u1Sri2d9/441-int-test-autocreate-robot-testdoc> > >> 3) Review test documentation strategy (we already have some stuff in place >> but maybe not working the way we want), spread this in the community and >> start enforcing things we need to meet the test documentation requirements. >> >> Comments? > > I really prefer to have as much documentation in our robot tests/libs as > possible. > > One thought I had for project deliverables around test plans: > > Can we ask projects to give us a real .robot suite(s) with their test plan? > They would not > have to be required to actually write the test cases at first, just the docs. > This need not > even be written by a test focused person, a developer type or architect type > could do it. > The test cases could be implemented at a later time.
IMO robot lacks a little bit of test organization (i.e. you only have 2 levels: suites and test cases) but on the other hand: 1) your idea brings devs closer to the test framework they will be using and 2) this way we do not need to maintain test plan outside robot, so I will +1. > > This would be a replacement to the existing "test plan" we ask for. > > bad idea? > > JamO > > >> BR/Luis >> >> >>> On Jan 30, 2017, at 1:19 PM, Robert Varga <n...@hq.sk> wrote: >>> >>> On 01/30/2017 04:59 PM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES >>> at Cisco) wrote: >>>> Current cluster suites do contain documentation, >>>> >>>> but it is focused on tester point of view only. >>>> >>>> I will be creating new integration/test: docs/ files >>>> >>>> to bridge the gap. >>>> >>> >>> It would be great to have these as test plans, so we can easily >>> cross-reference scenarios and have an understanding what our scenario >>> coverage is. >>> >>> Regards, >>> Robert >>> >>> _______________________________________________ >>> controller-dev mailing list >>> controller-dev@lists.opendaylight.org >>> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> >> _______________________________________________ >> controller-dev mailing list >> controller-dev@lists.opendaylight.org >> <mailto:controller-dev@lists.opendaylight.org> >> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> <https://lists.opendaylight.org/mailman/listinfo/controller-dev>
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
