A Defect Tracking System can save you from future issues that might get in between you and a perfect project. Watch this video and find out how a DTS works in the localization industry!
What’s up? What’s up everyone, this is Andrej from localization Academy. Welcome to the new localization basics. And this one, we’re going to talk about what the fuck is DTS.
DTS stands for defect tracking system. So tracking system is basically a system where we track defects, or otherwise known as bugs, or in general trumps issues. So where did the bugs market issues come from?
Well, let’s say we have our dear client, and a client sends us something to localize. Right, so we create the localized version of that. Now, we don’t want to just send a localized version straight to the world, because nobody has ever checked it, right? Imagine that you have software or application or website or whatever you have, and you just translated it.
But nobody actually tried to use the localized version, the same way that the end users, the clients, and the customers of the actual client will use it s. So that’s why we need to send it to QA, we need to test the localized versions, and our already covered QA. And and what QA people do is they basically go through the localized version, and they look for issues with it, what’s not working, what’s working worse than compared to the Source version of the product, or service.
And because many things can go wrong, they are collecting 10s, hundreds of different effects or bucks. So because of the sheer amount of issues that they encounter, we want to have some DTS, where all the different testers from across the world can come in, they can look or track the defects. And they can say whether this is a small like a minor bug, or if it’s critical, like we can even launch the application, and so on and so on. But it’s not only about the volume of the defects. It’s also about what happens to the bugs afterwards, right?
Somebody needs to actually look at the box, they might have some questions. So there needs to be a place for discussion. And then they want to fix it, once they fix it, we actually want someone to verify if it was fixed or not. So it can go back and forth and back and forth, and so on. So you need to also track the status of the bug where it’s a new bug, whether it was investigated, confirmed, whether it was resolved, and whether it’s confirmed and closed, and so on and so on.
So this will be very difficult to do through email, or even through spreadsheet, it will be possible but it’s better to have a dedicated system or a platform like JIRA or Bugzilla to handle all your defects across your different projects or products and so on. So, that is the DTS for you!