[Fiware-miwi] Status Integraton Test-Cases WP13

[Jarkko Vatjus-Anttila]

Hello,

I just got next to my email. Noon has already gone, and forge is down. So,
regarding to the fix mentioned below, we will take alook at that on monday.

- jarkko


On Fri, Feb 7, 2014 at 12:28 PM, Christof Marti <mach at zhaw.ch> wrote:

> Hi Stefano, Mauro
>
> I fixed the errors (removing or commenting out parts) and renumbered the
> test-cases.
> There were also some enhancement of some descriptions.
> Hope this is enough for a first delivery.
>
> We will continue to enhance the quality of the descriptions next week
> after the server migration.
>
> Best regards
> Christof
>
> Am 07.02.2014 um 10:01 schrieb Christof Marti <mach at zhaw.ch>:
>
> Hi Stefano, Mauro
>
> There is now content on the WP13 Integration test case page
>
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Advanced_Middleware_and_Web-based_User_Interface_enablers_-_Test_Cases_-_V3
>
> There are still 2 errors, which have to be fixed immediately and generally
> I am not yet satisfied with the quality of the test descriptions.
> I pushed again to fix and enhance the descriptions (see mail below), but I
> doubt this will be done until noon.
> Worst case I will remove the two test cases with errors at 11:00 and fix
> what I find. And enhance the other descriptions after the delivery.
>
> Best regards
> Christof
>
> Anfang der weitergeleiteten Nachricht:
>
> *Von: *Christof Marti <mach at zhaw.ch>
> *Betreff: **Status Integraton Test-Cases*
> *Datum: *7. Februar 2014 [6] 09:31:26 MEZ
> *An: *"FI-WARE, MiWi" <fiware-miwi at lists.fi-ware.eu>
>
> Hi
>
> Thanks to all who contributed to the Integration Test-Cases. I did not
> expect so many test-cases.
> When checking the page I found some errors and missing/weak parts, we
> should fix urgently.
>
>    - I2  3D-UI WebTundra → POI Data Provider) : Description for
>    Integration-Test I2 is missing (still template).
>    - 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“, …)
>    - I*nput Data* gives instructions, what has to be entered in this step
>    (examples: concrete data to be entered (string, xml, …), „load file from
>    http://xy“ <http://xn--xy-x2t/>, „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
>
> From: 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
>
>


-- 
Jarkko Vatjus-Anttila
VP, Technology
Cyberlightning Ltd.

mobile. +358 405245142
email. jarkko at cyberlightning.com

Go to www.cybersli.de and enrich your presentations!

www.cyberlightning.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140207/66b791a2/attachment.html>