It supports test automation, sharing of setup and shutdown codeįor tests, aggregation of tests into collections, and independence of the The unittest unit testing framework was originally inspired by JUnitĪnd has a similar flavor as major unit testing frameworks in other Thanks for reading, and if you have any questions, post on our forums.(If you are already familiar with the basic concepts of testing, you might want Unity2017.3.0f3 (Main publish version, which builds output files and asset bundles)Īll versions are tested to compile for Android, iOS, and UWP as well.Īs always, we will continue to periodically check for updates to each Unity version, as well as new versions.For supported versions, we will also answer questions on our forums, and debug issues reported by customers.Īs of today, the full list of versions we're testing with, are as follows: Support in this case being defined as: Our SDK builds are built with, and successfully execute a series of API tests, designed to demonstrate that the SDK is working across a wide feature set. Unity 5.3 was first published Dec 2015, which means we support just over the last two years of Unity versions. We needed to cut some old versions to reduce the build times, and the security issue gave us a convenient place to make the decision. All of it is automated, but it still lengthens the time it takes between building, testing, and publishing a new SDK.
There is a time and cost for testing so many versions of Unity. The rest of the reasons are mostly only relevant to PlayFab. Those installers will be forever vulnerable to that problem, and require executing their mitigation tool after installation. Unity has reported a security issue with older versions of Unity, and for the oldest ones, there will be no patch. However, we have decided to drop support for the oldest several Unity releases, specifically: 4.7, 5.0, 5.1, and 5.2Ī handful of factors have gone into this decision, but this is probably the biggest one: Specifically, the latest 4.x version (which has been 4.7.2 since May 2016), and every version higher. We also test many of the latest beta versions to make sure the next Unity version release will go smoothly for PlayFab customers. We understand the difficulty of upgrading your SDK versions, and your engine versions, so we have supported the widest variety we could. If you're on Unity version 5.3 or later, the rest of this blog post doesn't apply to you.įor almost two years, PlayFab has carefully maintained support for a wide variety of Unity versions.
If you in active development, using Unity 5.2 or older, this may be a good time to invest in updating your Unity version, and PlayFab UnitySDK version. PlayFab is removing support for Unity Versions 4.7 thru 5.2
0 kommentar(er)
