Migration guide from Sprimber 1.0.x to 1.1.x

Next steps should be performed for success migration:

1. Remove @EnableSprimber from main test automation application class. Now Sprimber uses Spring SPI-like mechanism to determine available auto-configurations. So, just sprimber-starter jar required in classpath
2. @Actions deprecated, since it was moved to the another package. Please use @Actions from com.griddynamics.qa.sprimber.discovery
3. @ScenarioScope moved to the package com.griddynamics.qa.sprimber.scope, the functionality remains the same
4. For multithreading customization, please add/replace bean testExecutor to the context instead of sprimberTestExecutor
5. If failed exceptions were customized for allure reporting, please rename the bean failedExceptionNames with nonPrintableExceptions