This first lesson serves as the foundation upon which the entire course will be built. It is critical to know what exactly Software is and how it is made up to properly understand the responsibilities of a Software Test Engineer.
This core course provides comprehensive understanding of the Software Development Lifecycle (SDLC), the roles and operations of a Software Tester / Quality Assurance Engineer. You will learn how the SDLC is used in several organizations to initiate software, gather requirements, design, develop and test applications.
You will learn how to analyze the Business Requirement Document (BRD), write Test Plans and Test cases, enter, assign and track defects (bugs) as well as all core Testing Types. In addition, you will learn how to write queries to extensively test the applications’ back-end database and validate the results. All topics are supported by hand-on exercises testing real-life applications.
This lesson gives you a comprehensive understanding of the Systems (Software) Development Lifecycle (SDLC). You will learn how the SDLC is used in several organizations to initiate software development, gather requirements, design, develop, test and launch applications.
Learn the two major types of Software Methodologies – Waterfall and Agile and why the latter is now the most widely used methodology. Also learn the major “umbrellas” of testing as it pertains to your path from entry level to an advanced level Test Engineer. The Instructor will walk you through your career path to a six figure income in Software Test Engineering using a typical Software Testing Organization chart.
This class will teach you how a Use Case is broken down to 3 major components – Actors, Goals and Dependencies and how the understanding of these 3 components will help you thoroughly analyze the Business Requirement Document and create exhaustive Test Cases.
Analyzing The Business Requirement Document (BRD) is a very crucial first step to becoming an expert Software Test Engineer. In this Video, the Instructor will teach you how to ensure that the BRD contains Testable and Measurable requirements that aren’t subjective or ambiguous. This knowledge will not only allow you to write exhaustive test cases, but will transition you from simply being a reactive tester (finding and reporting defect) to a proactive Quality Assurance engineer – proactively “injecting” quality to the Software from scratch.
Plan your work and Work your Plan. The Test Plan makes you do just that as it works you through the exercise of defining your Testing Goals and Objectives, Scope (in-scope and Out-of-Scope), Focus and Approach. It also help you define other items such as Exit and Entrance criteria and the project specifics such as schedule, communications etc.
At the core of every Software testing initiative is the creation (authoring) of exhaustive test scenarios documented in Test case document and then the execution. The extent to which a Software Test Engineer has thoroughly analyzed the BRD, identified multiple use cases and understood the nuisances of the system will greatly impact the quantity and quality of their Test cases. Be sure to watch this over and over again to get these much needed skills.
This part 1 of 2 video, covers 5 of the major Test Execution types most commonly used in the Industry and which serve as the basis of understanding how our Testing FOCUS dictates our APPROACH as discussed in the Test Plan training.
This part 2 of 2 videos, covers another 5 Test Execution types widely used in varying combinations in the Industry. The selection of one or more of these test types is usually determined by the system and project specifics.
In this overview, we go over the Defect Management process starting from what a Defect (a.k.a. Bug) is, how we carefully define items that will be documented in a Defect Tracking tool as a Defect, assign it’s priority and severity. We discuss a few Defect tracking tools with our focus on Bugzilla, which is used in this class.
In this Video, the instructor walks you step by step how to login to Bugzilla, understand the different components, enter a defect and assign it to the responsible party or parties and ultimately generating a report. We also cover how the defect is tracked through the system from the point where it’s entered to its closure.
In this Video, we cover the creation of the Test Summary Report which is the final document you will provide to the project team to summarize all your findings through out the Test phase of your project.