[Fiware-qualityassurance] Use of JIRA for tracking QA activities

[Davide Dalle Carbonare]

Dear Fernando,
  we're starting to use JIRA to track QA activities and starting from the
initial entries created by Clara I would like to propose a bit improved
naming convention that can fit the different needs.
Basically I wanted to follow a hierarchical view including at the end the
version under test and the type of test.
In case we need to ask or communicate something to the GEi owners we'll
create a ticket in their backlog and link it (thanks to jira relations) to
our ticket.
The names reported for the implementations are those you already shared
with us.

We ask your recommendation on how to proceed in a common and homogeneous
approach.
Everyone is welcome to contribute with comments.

We've just stared to create our tickets but in any case once we agree on a
common convention we'll rename them for compliance with the decision.

Kind Regards,
Davide


*the proposed pattern for the Summary of the ticket is:*

FIWARE.WorkItem.QA.<chapet>.<GE implementation name>.<version>.<test type>

*The variable fields are:*

<chapet>
Apps, Cloud, Data, I2ND, IoT, Security, WebUI, Ops, Academy, Catalogue

<GE implementation name>
Apps: ApplicationMashup, BusinessAPIEcosystem, Marketplace, Repository,
RSS, DataViz-SpagoBI, ApplicationMashup, Store, BusinessAPIEcosystem.
Cloud: CloudPortal, ResMgmt, Monitoring, ObjectStorage, PaaSManager,
PolicyMgr, SwDeployConfig, Murano, Docker.
Data: CEP, CKAN, BigData-Analysis, Stream-oriented, OrionContextBroker,
AeonCloudMessaging, MetaDataStoreManagementPlatform, SocialDataAggregator,
SocialSemanticEnricher.
I2ND: Kiara, OFNIC, Netfloc, Robotics
IoT: EPCGE, DataEdge-Cepheus, IDAS, BackendIoTBroker, IoTDiscovery
Security: AuthorizationPDP, CyberSecurity, IDM-KeyRock, PEP-Proxy, Privacy,
TrustworthyFactory
WebUI: AugmentedReality, CloudRendering, Fives, GISDataProvider,
InterfaceDesigner, POIDataProvider, RealVirtualInteraction,
Synchronization, VirtualCharacters, WebTundra3D, XML3D, 2D-3DCapture, 2D-UI
Ops: Dash, Deploy, Health, Toolkit
Academy: Builder, Platform, Player
Catalogue: Platform

<version>
numbering of the version dash-separated e.g. 1-3-0

<test type>
this field reflect the type of test to be executed also taking into account
the assignment to the different partner in the task
values are: functional, non-fuctional, documentation, catalogue, academy

*here is an example that we created in jira:*

FIWARE.WorkItem.QA.Data.OrionContextBroker.1-3-0.functional






Davide Dalle Carbonare
Senior Researcher - Big Data & Future Internet
Engineering Ingegneria Informatica S.p.A. - www.eng.it
Mob: +39-346-3207983
@davdalle <https://twitter.com/davdalle> | linkedin
<https://www.linkedin.com/in/davidedallecarbonare> | about.me
<http://about.me/davidedallecarbonare>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20170321/439c1f16/attachment.html>