[
https://issues.jboss.org/browse/ARQRUSH-33?page=com.atlassian.jira.plugin...
]
Lukáš Fryč edited comment on ARQRUSH-33 at 8/3/12 4:47 AM:
-----------------------------------------------------------
So there will be two representations of VisualSuite in memory:
- one corresponding to state of suite (suite.xml, A) - changed only on user input
- one corresponding to comparison results (result.xml, B) - changed during re-running
tests
Avoid to do bulk changes when VisualSuite changes. Only on particular user actions (click
to the image, run all).
was (Author: lfryc):
So there will be two representations of VisualSuite in memory:
- one corresponding to state of suite - changed only on user input
- one corresponding to results - changed during re-running tests
Avoid to do bulk changes when VisualSuite changes. Only on particular user actions (click
to the image, run all).
Refactor code to hold and use VisualSuite instance in memory as
representation of current state of suite
--------------------------------------------------------------------------------------------------------
Key: ARQRUSH-33
URL:
https://issues.jboss.org/browse/ARQRUSH-33
Project: Arquillian RushEye
Issue Type: Task
Components: Manager
Reporter: Lukáš Fryč
Assignee: Jakub Dunia
Fix For: 1.0.0.Alpha1
Currently, Manager works with custom representation of suite, which prevents to reuse
logic from Core for loading/writing.
The task is rewrite the implementation so that it will use Core as much as possible:
* loading/writing of VisualSuite
* representation and manipulation with VisualSuite directly
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira