[arquillian-issues] [JBoss JIRA] (ARQRUSH-26) Support detection of changes in cases and tests (removals, additions, modifications)

[Lukáš Fryč (JIRA)]

     [ https://issues.jboss.org/browse/ARQRUSH-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukáš Fryč reassigned ARQRUSH-26:
---------------------------------

    Assignee:     (was: Lukáš Fryč)


> Support detection of changes in cases and tests (removals, additions, modifications)
> ------------------------------------------------------------------------------------
>
>                 Key: ARQRUSH-26
>                 URL: https://issues.jboss.org/browse/ARQRUSH-26
>             Project: Arquillian RushEye
>          Issue Type: Feature Request
>          Components: Core, Manager
>            Reporter: Lukáš Fryč
>             Fix For: 1.0.0.Alpha1
>
>
> {quote}
> T 1341996997 31<lfryc>30	(5) problem of changes in test suite
> T 1341997028 31<lfryc>30	basically what to do when "screenshots1" and "screenshots2" differs
> T 1341997042 31<lfryc>30	in case of:
> T 1341997047 31<lfryc>30	a) test additions
> T 1341997050 31<lfryc>30	b) test removals
> T 1341997055 31<lfryc>30	c) test modifications
> T 1341997087 31<lfryc>30	the Manager should inteligently show the test case with matching images
> T 1341997100 31<lfryc>30	and even allow context-menu resolution
> T 1341997163 31<lfryc>30	we are currently investigating what's the stability of test suite (if the list of images doesn't differ between runs)
> T 1341997163 18<fafnir88>	if there is no corresponding image for test, this big image warning will be shown
> T 1341997204 31<lfryc>30	yeah, this would need to be more smart..
> T 1341997220 31<lfryc>30	let's see this case, you get those tests (images):
> T 1341997248 31<lfryc>30	00-open
> T 1341997248 31<lfryc>30	01-click
> T 1341997248 31<lfryc>30	02-click
> T 1341997248 31<lfryc>30	03-type
> T 1341997248 31<lfryc>30	04-click
> T 1341997248 31<lfryc>30	05-click
> T 1341997274 31<lfryc>30	but then you get other just those:
> T 1341997279 31<lfryc>30	00-open
> T 1341997283 31<lfryc>30	01-click
> T 1341997285 31<lfryc>30	03-type
> T 1341997304 31<lfryc>30	those images identifies all changes during the automated browser test
> T 1341997316 31<lfryc>30	then you have problem
> T 1341997321 31<lfryc>30	(sorry 02-type)
> T 1341997337 31<lfryc>30	the Manager could fallback to heuristics
> T 1341997359 31<lfryc>30	and in case of the images does not match in suite and samples..
> T 1341997378 18<fafnir88>	so, you want to have a test pruning for missing cases?
> T 1341997380 31<lfryc>30	it can offer alternative mode, when it could try determine what happened
> T 1341997390 18<fafnir88>	*test tree
> T 1341997394 31<lfryc>30	yep
> T 1341997402 31<lfryc>30	it should show something like:
> T 1341997407 31<lfryc>30	OK 00-open
> T 1341997412 31<lfryc>30	OK 01-click
> T 1341997434 31<lfryc>30	02-click (missing sample)
> T 1341997445 31<lfryc>30	02-type (missing pattern)
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)