Base knowledge - Jira Tutorial

- [Instructor] Whether you are a novice participating in a beta test, or you're a professional tester, trying to help your company get more value from your bugs. I'll help you navigate the steps of reporting issues discovered during your test. There are a few things that are helpful to know before we get started. First, you need to know the product you're testing. You don't have to be an expert, but you should be very competent, familiar with most of its core functionality and completely versed in its operation. Take time to carefully look over how the software works before you begin to test. In this course, I will talk about the processes of offering and managing bugs. You'll want to be able to correlate this to your own software and testing experience. As part of this course, I will also be using a sample application to help illustrate the process of testing and logging issues. Explore California is an all in one travel application for the state of California. The application is designed to provide both a web based and mobile experience for tourists visiting the state. I will be using this software to demonstrate bug creation. Next, you will be using a bug tracking software to share your discoveries. Make sure you're familiar with the system. Don't be intimidated by any bug tracking tools. Most are straightforward and don't require a lot of training. If you are testing in something like Jira or Center Code, the forms are easy to understand. However, if after this course is complete and you still have questions, reach out to your system administrator or project manager. One of the most popular of these systems for internal testing is Atlassian's Jira. This application is used worldwide and is very effective for bug management. Its flexible design and low cost for implementation have made it very popular. Throughout this course, we will also be using a sample database with our Explore California application to help you understand how to navigate the bug management process in Jira. Last, I don't delve too deeply into the structure of program management or development, but having some basic knowledge of these topics might help you. I use some common industry terminology and it's helpful to have insight on how the whole development process works and where bugs exist inside this process. While you are learning to write good bugs, the objective isn't about their quantity or even quality. Reporting good bugs is about helping your developing team deliver a refined and effective product. The issues you will be submitting directly impact quality and it's important you understand that you make a difference.