[
https://issues.jboss.org/browse/JBIDE-26455?page=com.atlassian.jira.plugi...
]
Pavol Srna updated JBIDE-26455:
-------------------------------
Description:
The tool is to support new test strategy for devstudio:
{quote}
In the current approach we do a full test cycle on all components with every milestone.
This includes also manual steps, etc. and it is resource and time demanding. However some
of the components have zero activity, or only a few commits per train. The idea is to
limit the testing on low activity components and focus more on the new stuff - like
adapters, where it has more value for the current product offering. We do not plan to stop
the testing completely. We will monitor github repositories for significant changes. In
case we find out there is a significant change on the repository, we will include the
component in the milestone testing.{quote}
was:
The tool is to support new test strategy for devstudio
{quote}
In the current approach we do a full test cycle on all components with every milestone.
This includes also manual steps, etc. and it is resource and time demanding. However some
of the components have zero activity, or only a few commits per train. The idea is to
limit the testing on low activity components and focus more on the new stuff - like
adapters, where it has more value for the current product offering. We do not plan to stop
the testing completely. We will monitor github repositories for significant changes. In
case we find out there is a significant change on the repository, we will include the
component in the milestone testing.{quote}
Implement monitoring Tool for watching changes in jbt repositories
and dependency changes in TP
-----------------------------------------------------------------------------------------------
Key: JBIDE-26455
URL:
https://issues.jboss.org/browse/JBIDE-26455
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Affects Versions: 4.10.0.AM1
Reporter: Pavol Srna
Priority: Major
The tool is to support new test strategy for devstudio:
{quote}
In the current approach we do a full test cycle on all components with every milestone.
This includes also manual steps, etc. and it is resource and time demanding. However some
of the components have zero activity, or only a few commits per train. The idea is to
limit the testing on low activity components and focus more on the new stuff - like
adapters, where it has more value for the current product offering. We do not plan to stop
the testing completely. We will monitor github repositories for significant changes. In
case we find out there is a significant change on the repository, we will include the
component in the milestone testing.{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)