We have updated our End User License Agreement (EULA).
The new EULA is more generic about the product it refers to, that is now generally “SpecSync”, the same EULA is used for “SpecSync for Azure DevOps” and “SpecSync for Jira”. We have clarified the optional statistical data that we might collect to improve our services and this contains no personal or project data or data that makes the client identifiable (section 1/f). We have also included an option to verify the license usages online, by sending license usage data, but no identifiable user names or project details (section 1/g). The new EULA will take effect on 1st May 2023. Please check the updated EULA and contact us if you have any concerns about it.
A few weeks ago we announced the planned Test Suite synchronization feature and asked you to fill out a survey about your expectations. The survey is still open, but we would like to present some preliminary results and a new preview feature that is available in the new version v3.4.3 that has just been released.
We have introduced the survey because my experience so far was that there is no one-size-fits-all solution when it comes to the hierarchies the different teams use to organize their test cases. The survey result so far has reinforced my experience. Besides that practically all responders found important to have such a feature in SpecSync, for all the other questions we have got diverse expectations without a clear “winner” from any of the options we outlined there. This is an important input and signals that we have to concentrate on two things with this feature.
1) A “simple” solution will not be satisfactory for most of the users. We need to provide detailed configuration options.
2) We will not be able to match all expectations at once (or better to say with a single feature), but we need to incrementally provide more and more options for synchronizing hierarchies.
Along this strategy in the new update release v3.4.3 we included a new customization feature, called Add Test Cases to Suites. This can be considered as a preview feature of the full hierarchy synchronization, but pretty powerful already. You can list multiple Test Suites where the synchronized Test Cases should be included. It does not remove “other” Test Cases from the Suites (e.g. the ones you have added manually) but if it is able to detect that a synchronized scenario has been removed, it will remove it from the Suite. The Test Cases to be included can be specified using “local test case conditions” (introduced in v3.4) where you can combine tag expressions and file path expressions. For example including all Test Cases of the scenarios that are tagged with @important and that are inside the pricing folder to a suite named “Pricing”, you can use the following configuration.
{
…
“customizations”: {
“addTestCasesToSuites”: {
“enabled”: true,
“testSuites”: [
{
“name”: “Pricing”,
“condition”: “@important and $sourceFile ~ pricing/”
}
]
}
}
…
}
As always, we are looking forward to your feedback.
Have a great week!