OK, everybody. Thank you for stopping by. We're going to talk about introducing a new feature inside Toad for Oracle. It's inside Toad for Oracle base to all of the advanced editions coming out. So it's not something that costs more. And it's a utPLSQL unit tester.
So I'm going to start with this question. This is a question we sent out to a survey very recently to our Toad for Oracle development group and said, is writing unit tests for PLSQL code important? Three possible answers. What do you guys think? Guess? Yes. What do you think-- 50%, 80%, 90%? OK.
Well, our answers are that 61% of our users said yeah, this is important. 20% flat out said no, which is strange, because I would expect it to be higher. And 20% said that it depends. So then, we followed up with this one. Are you currently doing it? Are you writing unit tests to accompany your PLSQL code? Yes/no answer. Any guesses? Yeah, it was 50/50. Right? So about 53 were actually doing it, which of course leads to this discrepancy. Even of the folks who said it was important, only 70% are actually doing it today. So, yeah it's important, but not doing it.
So the next follow up question we had was why. Tell me, if you're not doing writing unit tests for your code, why? Top answer, no time. All right? I just get the code done, consider it works. I test it, it's good enough. Number two, lack of tools to make it easy. Number three, not a priority for the business, which I assume has to do with the fact it takes time. Right? And then the last one was not sure how to do it.
So we looked at that, and it looked like a great problem that as a vendor, we could help you solve. Right? We could really focus in on these items. And so just really quickly, why do we care about unit tests? Why is this a big deal? First of all, we know we don't want bugs in our code. Right? So we have to do testing at least for that. But the second one is when it comes to database DevOps. Right? Database DevOps is coming more and more into our consciousness of how we had to do things faster, but incurring less risk. Right? And so, you can not do database DevOps against PLSQL code if you cannot automate the testing. And you cannot automate the testing if they do not exist. Right? The tests don't exist.
So database DevOps needs unit tests, because database code is code. Right? It's not a database, and it's not a database component. It is code. Every successful DevOps, you need high quality code. One way to ensure high quality code is by having high code coverage, so that you know every line of code that you've written is being tested. And to get high code coverage, you need unit tests for your PLSQL code. Right? Really simple logic, right? If you want to have that consistent quality in your code and you want to push it to production faster, unit test creation is the way to go.
And in short, if you're writing your PLSQL without unit tests-- I don't want to call you out by name, sir, but we already talked about this earlier. As you increase your database code, you are reducing your DevOps readiness. Right? You're incurring debt that's going to have to be picked up at a later time. So we want to avoid that.
So let's focus in on these three things here. No time, lack of tools, and not sure how to do it. And let's talk about how Toad can help. So we actually already have a code tester for Oracle. This is part of one of our higher editions of Toad in the Development Suite. If you are doing a test-driven development, and you're writing your tests first, then this is a great option, if you don't already have it.
But we are now introducing utPLSQL integration into every edition of commercial Toad, from base all the way through. Right? So you don't have to have a special edition of Toad. We're integrating with utPLSQL. What is utPLSQL? It basically is JUnit, but for PLSQL code. There is an organization out there. It's open source. It's an open source framework. It was actually developed originally by Stephen Feuerstein, who actually developed our code tester as well-- the one that's in the higher edition. And it's a really robust open source community. It's being well managed out there, so it's growing regularly.
So in Toad for Oracle plus utPLSQL, you now can install utPLSQL straight from the Toad for Oracle menu. And I'll show you that menu in a second. You can create test suites and unit tests. You can run all of those tests for real time results. You can browse all of your tests. You can run your imports from there, including a code coverage report. So you could point at any schema in your environment, and it will tell you what your code coverage is for the test for the PLSQL code in that environment.
This is all available in Toad for Oracle 13.2, which will GA in a little over a month now. OK. So what I want to call out here is this is a Toad for Oracle menu. Should look very familiar to you guys. And you're going to see right up there at the top, right next to Team Coding. We have that unit testing menu. That's going to show up in everybody's Toad for Oracle when you upgrade to 13.2. And you can see right there, you can install your utPLSQL. You can create your unit tests, and you can go to your unit test manager. OK? So it's going to be right there in your UI.
Because we did hear that we don't know how to do unit tests or the right methodologies to use, we've included walkthroughs with every portion of this. So when you go to create a test suite, we're going to give you all the variables that you need to add to create that initial code. Same thing when you go to create test cases. And unit tests-- we're going to give you all those variables that you need to add so you can create the initial code.
And then, we're also including pop up menus which give you video recordings about how to create unit tests, and the right kind of sequencing that you need to use, and the right kind of methodology to create good, useful unit tests. There's a unit test manager where you can browse all the unit tests you've created by suite. You can run them and see what their status is, including if they failed. You can get more reports about why they failed. And then again, you can run your codes and get your code coverage. So you can see how many lines of your code are actually covered by your unit test.
And that's it. So I just wanted to call out. This is available for Toad for Oracle in 13.2 in November. And we'll continue to enhance this throughout all of our releases. And so if you're using Toad for Oracle today, if you have a copy on your desktop, it's something you can start using in November. It's available to everybody. Thank you, guys.