[
https://issues.apache.org/jira/browse/AURORA-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Cohen updated AURORA-1609:
---------------------------------
Description: As revealed by AURORA-1603, we're not always as rigorous as we
should be about ensuring compatibility between commits. It would be great to
run automated tests that ensure that rollbacks between commits (and between
releases!) are possible. It should be possible to update the end to end tests
to finish off by reverting to the previous commit, rebuilding and restarting
the scheduler, then ensuring everything starts up cleanly. Once AURORA-1608 we
can automate this by having e2e tests run as part of our CI job. (was: As
revealed by AURORA-1603, we're not always as rigorous as we should be about
ensuring compatibility between commits. It would be great to run automated
tests that ensure that rollbacks between commits (and between releases!) are
possible. Once we have AURORA-1608 done, it should be possible to update the
end to end tests to finish off by reverting to the previous commit, rebuilding
and restarting the scheduler, then ensuring everything starts up cleanly.)
> Create automated rollback testing
> ---------------------------------
>
> Key: AURORA-1609
> URL: https://issues.apache.org/jira/browse/AURORA-1609
> Project: Aurora
> Issue Type: Task
> Components: Testing
> Reporter: Joshua Cohen
>
> As revealed by AURORA-1603, we're not always as rigorous as we should be
> about ensuring compatibility between commits. It would be great to run
> automated tests that ensure that rollbacks between commits (and between
> releases!) are possible. It should be possible to update the end to end tests
> to finish off by reverting to the previous commit, rebuilding and restarting
> the scheduler, then ensuring everything starts up cleanly. Once AURORA-1608
> we can automate this by having e2e tests run as part of our CI job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
