At the heart of every software project is the user. If the user finds the software confusing, or if it doesn’t do what the user needs it to do, what’s the point? 이런 이유로, user testing is an essential part of the development process.
User testing can involve a range of activities. You might watch how users interact with the software. You might track or monitor how they use it. And you might ask them for their opinions. 이런 식으로, you collect information and feedback that helps you create the best user experience possible. And just as the software itself needs to be user friendly, so does user testing. If people don’t have a clear idea of what they’re supposed to do during testing, you’ll be wasting an opportunity.
So when you launch testing, it’s important to outline what you’re going to be doing, and what kind of feedback you’re interested in. Because the software is new to the test users, you’ll need to give them clear instructions on how to use it and give them an overview of the main features. You might also find yourself emphasizing key points along the way. 아무튼, it’s much easier to make sure everyone understands upfront than to deal with confused users during testing.
오늘 대화에서, 우리는 Jill을 듣습니다, a developer with a software company called OptiTech. They’ve been developing software for a logistics company, and now they are ready to launch the first round of user testing. We’ll also hear Liam, 클라이언트의 IT 관리자, and Carla, one of the test users.
1. What does Jill say will be the final step in this test?
2. What three aspects of the software does this test focus on?
3. What does Jill emphasize is absolutely necessary for the drivers to do?