We often get requests to explain how we test the engine before we release it. We have previously blogged about it, but none of these posts g... 더 읽기

It’s been 1.5 years since we last did an incident bash, so time was ripe for executing another in order to get some fresh data. Enter the Gr... 더 읽기

The QA mini site is a one stop place for our blogs, our public test suites, the Unity Test Tools and the patch releases. You will be able to... 더 읽기

In January we merged the QA and Support teams into one organization with me (QA Director) heading them. The main purpose of this merge was t... 더 읽기

Thus we made the decision to make Unity Test Tools available for our users, which we hope will help you attain a high quality in your code... 더 읽기

Due to popular demand, we have decided to open our bug database to the public. Take a look at the issue tracker and vote on the bugs that ar... 더 읽기

We wanted answers to a few questions: How many bugs can we find in those reports? How good is our rating system? (brief explanation be... 더 읽기

Recently our CEO David Helgason gave a presentation at Unite Nordic where one of the key points was that Unity is having a huge focus on qua... 더 읽기

Our next upcoming release is Unity 4.2. Without actually going into what it's going to contain in terms of features, let's take a look at th... 더 읽기

The Problem In the previous 2 releases, 4.0 and 3.5, we had a very, very long release cycle. 4.0 work was started in January 2012 for some ... 더 읽기

In the aftermath of all the features and goodies Unity 4.0 will give you, I’d like to bring you the story of how the quality assurance, or “... 더 읽기

Time has come for a deeper dive into the number crunching that is also a part of being in quality assurance. I like numbers. I love spreadsh... 더 읽기

Time for the second installment of what testing Unity is like (first one here). As mentioned in the previous post we have STEs (Software Tes... 더 읽기