unity手动激活
Hello everyone, my name is Agnieszka Loza, I’m one of the QA Leads at Unity. I’d like to present to you the Software Test Engineers team (STE). If you are interested in how our army of testers works, you may have already seen the articles about the SDET and Toolsmith teams from Elvis and Kasper. Or maybe you have read my previous post about the STE team offsite.
大家好，我叫Agnieszka Loza，我是Unity的质量检查主管之一。 我想向您介绍软件测试工程师团队(STE)。 如果您对我们的测试人员队伍的工作方式感兴趣，您可能已经看过Elvis和Kasper的有关SDET和Toolsmith团队的文章。 或者，也许您已经阅读了我以前关于STE团队不在现场的帖子 。
The STE team is a sub team of our QA department. There are 20 testers in our team, working from Unity offices in Copenhagen, Odessa, Vilnius, Montreal, Boston, Berlin, and a few more locations. We are, what you may call, manual testers but there is much more to it than that. In this post, I’d like to tell you about the responsibilities we have and the activities we carry out. I will tell you a story about how STE team contributes to the never ending battle for better quality!
STE团队是我们质量检查部门的子团队。 我们团队中有20位测试人员，分别在哥本哈根，敖德萨，维尔纽斯，蒙特利尔，波士顿，柏林以及其他几个地方的Unity办事处工作。 我们就是您所说的手动测试仪，但除此之外，还有更多。 在本文中，我想向您介绍我们的职责和开展的活动。 我将告诉您一个有关STE团队如何为永无止境的争夺战做出更好贡献的故事！
责任与挑战 (Responsibilities and challenges)
Unity is a big and complex software. In order to make it more testable, we divided it into areas – every area is a distinct chunk of functionality. To give a few examples, 2D is an area in Unity, so are: Animation, Terrain, Asset Import, Particle System, PS4, Xbox, UI, Shaders and so on. All in all, there are around 70 areas. Every area has a designated STE and at least one backup STE who are responsible for planning and carrying out all the necessary test activities related to it.
Unity是一个庞大而复杂的软件。 为了使其更具可测试性，我们将其划分为多个区域–每个区域都是不同的功能块。 举几个例子，二维是Unity中的一个区域，动画，地形，资产导入，粒子系统，PS4，Xbox，UI，明暗器等等。 总共大约有70个区域。 每个区域都有一个指定的STE和至少一个备用STE，负责计划和执行与之相关的所有必要测试活动。
To be able to create and execute a test strategy for an area, STEs have to be knowledgeable on many fronts. They must know about Unity – especially the area they work on, but also about the ways the area’s functionality interacts with the rest of the engine. They need to know test techniques and how to properly apply them to retrieve the information they’re looking for. Technical knowledge is also required of an STE – they don’t always code on their own, but they need to understand basic programming concepts and be able to do some coding, when that’s required. Finally, knowing about the game industry is also a big advantage. Knowing how game developers use Unity and the expectations they have of the engine is a great source of testing inspiration.
为了能够创建和执行某个区域的测试策略，STE必须在很多方面都具有丰富的知识。 他们必须了解Unity，尤其是他们所从事的领域，还必须了解该领域的功能与引擎其余部分的交互方式。 他们需要了解测试技术，以及如何正确应用它们以检索所需的信息。 STE也需要技术知识–他们不一定总是自己编写代码，但是他们需要了解基本的编程概念，并能够在需要时进行一些编码。 最后，了解游戏行业也是一大优势。 了解游戏开发人员如何使用Unity以及他们对引擎的期望是测试灵感的重要来源。
Testers take all these considerations into account and create a test strategy defining what needs to be tested and how to test it. They use what they know and draw a map – a plan of how they will look for landmines (read: bugs). They try to figure out what they don’t know and scout around to retrieve missing information.
测试人员会考虑所有这些考虑因素，并创建一个测试策略，定义需要测试的内容以及如何对其进行测试。 他们利用所了解的知识绘制地图-他们计划寻找地雷的计划(阅读：虫子)。 他们试图找出自己不知道的内容，并四处寻找丢失的信息。
测试中 (Testing)
STEs are active from the early stages of developing a new feature. They work closely with developers of their areas and are the first ones to look at the feature in progress – long before it goes into a release or reaches the alpha group. The main task of a tester is to become familiar with the new features, consider related risks and provide comprehensive feedback such as suggestions for improved workflows, discovered bugs and comments on learnability etc. The Test Engineer’s job is to provide an initial evaluation of the quality that will help to make the call whether the feature is ready to be included into a release or not.
STE在开发新功能的早期就很活跃。 他们与各自领域的开发人员紧密合作，并且是第一个查看正在开发中的功能的人-早在发布或进入alpha组之前。 测试人员的主要任务是熟悉新功能，考虑相关风险并提供全面的反馈，例如改进工作流程的建议，发现的错误以及对可学习性的评论等。测试工程师的工作是对质量进行初步评估。无论该功能是否已准备好包含在发行版中，这将有助于拨打电话。
Once the feature is in a release, more elaborate testing continues. STEs research all the possible risks related to new features and based on this analysis they test, focusing on the functionality that may be shaky or yet unexplored. Testers work in pairs. They use more challenging test data and look at complex user scenarios and integration with other features. It is also a good way to ensure we have a fresh pair of eyes on most new features. During this phase, testers strive to uncover all the critical problems.
该功能发布后，将继续进行更详细的测试。 STE研究与新功能有关的所有可能的风险，并根据他们测试的分析结果，着眼于可能不稳定或尚未开发的功能。 测试人员必须成对工作。 他们使用更具挑战性的测试数据，并研究复杂的用户场景以及与其他功能的集成。 这也是确保我们对大多数新功能有新的了解的好方法。 在此阶段，测试人员努力发现所有关键问题。
Based on the testing done in the alpha phase, STEs create manual test cases that will be used later on, in beta and release candidate phases, to catch possible regressions. Even though the main focus of these phases is on polishing the features and on bug fixes, we still run the risk that the code changes will cause regressions. Every STE is designing and creating the regression test suites for their areas, making sure that the coverage is sufficient, and that the manual test cases do not overlap with automation testing – which would be redundant.
基于在Alpha阶段进行的测试，STE创建了手动测试用例，稍后将在Beta和发布候选阶段中使用它们以捕获可能的回归。 即使这些阶段的主要重点是完善功能和错误修复，我们仍然冒着代码更改将导致回归的风险。 每个STE都在为其所在区域设计和创建回归测试套件，以确保覆盖范围足够，并且手动测试用例不会与自动化测试重叠-这将是多余的。
Other testing activities include Release Acceptance Testing (RAT) and bug verification. RAT is a very narrow set of manual regression tests focused on detecting critical bugs in the builds that we are about to release – either to the public or to the alpha and beta users. Bug verification is a frequent area-grooming activity – testers verify fixed bugs, they investigate those that were deferred and close the ones that are no longer reproducible. Knowing the bug situation for the area is one of the metrics we use to evaluate the quality of the area.
其他测试活动包括发布验收测试(RAT)和错误验证。 RAT是一组非常狭窄的手动回归测试，专注于检测要发布的版本中的关键错误-面向公众或Alpha和Beta用户。 错误验证是一项经常进行的区域修饰活动-测试人员验证固定的错误，他们调查延迟的错误并关闭不再可复制的错误。 了解该区域的错误情况是我们用来评估该区域质量的指标之一。
报告中 (Reporting)
During all three stages of a release – alpha, beta and release candidate – testers report back from the testing front. There is a lot of interesting stories a tester can tell. What is the status of a given feature? Is it ready to be used? How does the feature perform under various scenarios? Is the feature doing what is supposed to do? Is it compatible with all related functionality? What do the users think of it? What is the number of known bugs? What’s the trend in regressions? How severe are the problems the feature still has? All these different questions – and more – are answered by the STEs in the area reports they send out thrice per release.
在发行的所有三个阶段(alpha，beta和候选发行版)中，测试人员都会从测试方面进行报告。 测试人员可以讲很多有趣的故事。 给定功能的状态是什么？ 准备好使用了吗？ 该功能在各种情况下的性能如何？ 该功能正在执行应做的事情吗？ 它与所有相关功能兼容吗？ 用户对此有何看法？ 已知错误的数量是多少？ 回归趋势如何？ 功能仍然存在多严重的问题？ 所有这些不同的问题(甚至更多)都由STE在每个报告中发出三次的区域报告中回答。
Who reads these reports? Everyone! Developers, release managers, testers, test managers, release coordinators, executive team – everyone who has the interest in the quality of the software or has to make decisions regarding development and shipping of Unity.
谁阅读这些报告？ 大家！ 开发人员，发布经理，测试人员，测试经理，发布协调员，执行团队–每个对软件质量感兴趣或必须就Unity开发和交付做出决定的人。
任务 (Mission)
STE Team provides a unique service. We collect and present the feedback about the quality of the Unity engine so that everyone can be better informed in making decisions. Our goal is to support Unity Technologies and we do so to the best of our abilities and available resources.
STE团队提供独特的服务。 我们收集并提出有关Unity引擎质量的反馈，以便每个人都能更好地制定决策。 我们的目标是支持Unity Technologies，并尽我们最大的能力和可用资源。
The team continually seeks to learn new skills and improve the testing toolbox to support the goal stated above. We go to various courses, training sessions and conferences. We share knowledge within the group on a weekly basis and we strive to improve our processes.
团队不断寻求学习新技能并改进测试工具箱以支持上述目标。 我们参加各种课程，培训课程和会议。 我们每周在小组内分享知识，并努力改善流程。
This was a summary of how the STE team stays busy – by testing, reporting and learning – all oriented around supporting Unity Technologies in making strategic business decisions. If you find this tester profile interesting feel free to contact us! We are hiring!
总结了STE团队如何通过测试，报告和学习来保持忙碌状态，这些工作全部围绕支持Unity Technologies制定战略业务决策而进行。 如果您发现此测试仪配置文件有趣，请随时与我们联系！ 我们正在招聘！
unity手动激活
391
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
