On 07 Feb 2014, at 10:31, Christof Marti <mach at zhaw.ch> wrote: > I2 3D-UI WebTundra → POI Data Provider) : Description for Integration-Test I2 is missing (still template). I don’t know whether the POI folks want to have this up there or not. If it’s only up to us on the 3D-UI side, let’s just delete it (for now). If the POI team wants to have that there we can help with documenting it if needed. We can fill in more details to the 3D-UI - Sync one if needed. The details are already in the manuals which are linked, do you suggest we copy-paste and not link? ~Toni > I7 3D-UI XML3D → MIWI Dataflow process (WebCL) GE : Dataflow process (WebCL) is not a GE > Also I find the description of the Test-Cases is to unspecific in most cases and lacks some details > Input Specification should describe what is the input for the test case (data format description, inline examples, file references, …) > Output Specification describes what will be the result of the process (data format description, inline examples, textual description what is displayed, …) > Environmental needs describes the prerequisites to start the test (Services/GEs installed and running, references to other tests which have to be executed before, other infrastructure needed (Android, or human operator doing something). > In the steps section, the detailed steps through the process should be described: > Details contains the short description, what will be done (examples: "Login to xy“, „Load scene file“, „Navigate to demos section“, …) > Input Data gives instructions, what has to be entered in this step (examples: concrete data to be entered (string, xml, …), „load file from http://xy“, „Click on demo x“,…) > Expected Result shows what will be the result at the end of this step (examples: concrete data returned, what page will be shown, Description of something happening in a scene,…) > For the steps expect that the GEs (specified in Environmental Needs) are already installed and running according to the Installation Guide. So here only the steps to execute the test are required. > > In general we need more specific data in the input sections (Files to be loaded from where, URLs to be accessed, Data to be entered, …) > I prefer to have less Integration tests, but better quality of the description (approx 3-5 tests with good detailed description) > If the details of a test-case are not yet available, we better add the dependency chain to the "Planned dependencies for further versions“ table. > > The first two problems have to be fixed immediately. > And we should enhance the description of test cases which are mature enough until noon (or move the Test-Case to Planned table). > Who is able to enhance which tests until noon? > > Best regards > Christof > > Am 05.02.2014 um 13:29 schrieb Christof Marti <mach at zhaw.ch>: > >> [Tomorrow Thu Feb 6th 12:00 CET] All GEi owner: Add GE-Integration chain & Integration test description using your GE to the MIWI integration wiki page: >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Advanced_Middleware_and_Web-based_User_Interface_enablers_-_Test_Cases_-_V3 >> I added the basic structure and template for the test cases. You only need to add your integration chain and update the test-case description. >> Instructions & examples of other chapters: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Integration_Plan > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140207/a63582a5/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy