[ 
https://issues.apache.org/jira/browse/ISIS-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361137#comment-16361137
 ] 

ASF subversion and git services commented on ISIS-1569:
-------------------------------------------------------

Commit c2026ee3cbbbdf6e6a413017a8cd4440bca72c4a in isis's branch 
refs/heads/maint-1.16.1 from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=c2026ee ]

ISIS-1569: suppresses possible concurrency exceptions when auditing pre-commit.


> Automated testing tool to replay commands against a copy of prod
> ----------------------------------------------------------------
>
>                 Key: ISIS-1569
>                 URL: https://issues.apache.org/jira/browse/ISIS-1569
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.13.2.1
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Major
>             Fix For: 1.16.1
>
>
> eg obtain copy of prod from a month ago
>  then for all commands since then, replay (simulating the current user and 
> time for each)
>  finally, compare resultant database with current prod, and list out 
> differences in data.
> could also use for performance testing, perhaps.
>  
> ~~~
> most of the implementation is in the Incode Platform, command and 
> command-replay modules.
> Changes in Isis to support this are:
>  * CommandWithDto sub-interface of Command
>  * @Action(commandDtoProcessor=...)
>  * @Property(commandDtoProcessor=...)
>  * implementations of ContentMappingServiceForCommandDto and 
> ContentMappingServiceForCommandsDto
>  * CommandDtoProcessorService SPI as used by the former to allow the 
> CommandDto to be enhanced
>  * extensions to cmd.xsd for userdata and commands
>  * factored new superclass CommandExecutionAbstract from 
> BackgroundCommandExecution, subclassed by new quartz job when replay is 
> enabled
>   
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to