프로젝트가 확장되고 프로젝트의 스크립트, 클래스 및 메서드 수가 늘어남에 따라 코드의 한 부분을 변경할 때 다른 곳에서 문제가 발생하지 않도록 만들기 어려울 수 있습니다.
자동 테스트를 사용하면 코드의 모든 부분이 예상대로 작동하는지 확인할 수 있습니다. 수동 테스트 또는 최종 사용자의 버그 보고서에 의존하지 않고, 개발 중에 문제가 발생하는 즉시 발생한 위치와 시점을 식별하여 시간을 절약합니다.
Unity 테스트 프레임워크 패키지(구 “Unity 테스트 러너”)는 Edit 모드와 Play 모두에서 코드를 테스트하며, 스탠드얼론, Android, iOS와 같은 타겟 플랫폼에서도 사용 가능한 툴입니다.
테스트 프레임워크 패키지의 다른 버전에 대한 자세한 내용은 com.unity.test-framework 페이지를 참조하십시오.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.