Course

Quality Assurance Manual Testing

This course is a comprehensive introduction to Software Testing and Quality Assurance. During the 20 classes you will learn: Software Development Methodologies, the Role of Quality Assurance in a Software Development Life Cycle.

Starting at $1,800

Starting Date:

January 8, 2020

Format:

• Live training (on-site)
• Project-based collaborative training
• Hands-on, agile approach

Schedule/ Location:

• Mondays and Wednesdays
• 6.00PM – 9.00PM
• Location: 222 S Riverside Plaza, Chicago IL 60606 (Suite 2800)

Course Introduction


This course is designed with the novice tester in mind. Whether you’re completely new to software development or have experience in other areas of software development and are now considering a move into the testing field, the materials are intended to give you a basic understanding of the software testing process and insight into your role and responsibilities as a professional software tester.

Who teaches the courses?

Ricardo is a seasoned QA engineer with more than 16 years of experience in the software industry, working in projects ranging from mobile, desktop, and web applications to large scale enterprise solutions for services, printing, and logistics. Ricardo is proficient in test automation of both backend and frontend applications. He loves solving problems by taking advantage of cutting edge strategies and methodologies and developing testing tools and frameworks.

Ricardo Staudt

Quality Assurance (QA) Instructor

Who teaches the courses?

Course Program 60 hours


  • QA Testing Introduction | hours of theory ∙ hour of practice

    Let’s start with the basics of testing and introduction to the profession. For six lessons, you will get acquainted with the theory of testing, learn the difference between the concepts of QA and testing, and begin to write test scripts and start bugs. In practice, you will work with various software products, create test scripts for them in Zephyr and start bugs on the JIRA platform, as well as test the API.

  • Software Testing Basics | hours of theory ∙ hour of practice

    Software that does not work correctly can lead to many problems, including the loss of money, time, or a business’s reputation. Software testing is a way to assess the quality of the software and to reduce the risk of software failure in operation. Executing tests can show failures that are caused by defects in the software. Debugging is the development activity that finds, analyzes, and fixes such defects. Subsequent confirmation testing checks whether the fixes resolved the defects. In Agile development and in some other lifecycles, testers may be involved in debugging and component testing.

  • Types of Testing | hours of theory ∙ hour of practice

    A test type is a group of test activities aimed at testing specific characteristics of a software system, or a part of a system, based on specific test objectives.

     

    • Functional testing of a system involves tests that evaluate functions that the system should perform.
    • Non-functional testing of a system evaluates characteristics of systems and software such as usability, performance efficiency or security.
    • White-box testing derives tests based on the system’s internal structure or implementation. Internal structure may include code, architecture, work flows, and/or data flows within the system.
    • Confirmation testing: After a defect is fixed, the software may be tested with all test cases that failed due to the defect, which should be re-executed on the new software version.
    • Regression testing: It is possible that a change made in one part of the code, whether a fix or another type of change, may accidentally affect the behavior of other parts of the code.
  • Testing Life Cycle | hours of theory ∙ hour of practice

    Software Testing Life Cycle (STLC) is defined as a sequence of activities conducted to perform Software Testing.

     

    • Requirements Analysis
    • Test Planning
    • Test case development
    • Test Environment setup
    • Test Execution
    • Test Cycle closure
  • Test Development | hours of theory ∙ hour of practice

    During test design, the test conditions are elaborated into high-level test cases, sets of high-level test cases, and other testware. So, test analysis answers the question “what to test?” while test design answers the question “how to test?” Test design includes the following major activities:

     

    • Designing and prioritizing test cases and sets of test cases
    • Identifying necessary test data to support test conditions and test cases
    • Designing the test environment and identifying any required infrastructure and tools
    • Capturing bi-directional traceability between the test basis, test conditions, test cases, and test procedures
  • Test Case Design | hours of theory ∙ hour of practice

    Test design results in test cases and sets of test cases to exercise the test conditions defined in test analysis. It is often a good practice to design high-level test cases, without concrete values for input data and expected results. Such high-level test cases are reusable across multiple test cycles with different concrete data, while still adequately documenting the scope of the test case. Ideally, each test case is bidirectionally traceable to the test condition(s) it covers.

  • Test Execution | hours of theory ∙ hour of practice

    During test execution, test suites are run in accordance with the test execution schedule. Test execution includes the following major activities:

     

    • Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware
    • Executing tests either manually or by using test execution tools
    • Comparing actual results with expected results
    • Analyzing anomalies to establish their likely causes (e.g., failures may occur due to defects in the code, but false positives also may occur
    • Reporting defects based on the failures observed
    • Logging the outcome of test execution (e.g., pass, fail, blocked) and others.
  • Software Development Life Cycle | hours of theory ∙ hour of practice

    A software development lifecycle model describes the types of activity performed at each stage in a software development project, and how the activities relate to one another logically and chronologically. Different software development lifecycle models often have different ways of organizing the testers and test activities. Having some of the test activities done by independent testers increases defect detection effectiveness, which is particularly important for large, complex, or safety-critical systems. Independent testers bring a perspective which is different than that of the work product authors (i.e., business analysts, product owners, designers, and programmers), since they have different cognitive biases from the authors.

Does it Fit You?


As a tester, you will become an important part of the IT product development team. At the same time, mastering the profession is much easier than becoming a programmer.
As a tester, you will become an important part of the IT product development team. At the same time, mastering the profession is much easier than becoming a programmer.
As a tester, you will become an important part of the IT product development team. At the same time, mastering the profession is much easier than becoming a programmer.

Skills You Will Gain


Learn to do unit testing

Learn how to create a UI testing project

Get to know the tools: Selenium, Selenide, Akita

Master running tests in docker containers

Master the basics of SQL

Learn the principle of BDD when developing test scripts

Learn to work with reporting systems, Report Portal

Students Review


There are two important things that one needs to have when thinking of starting a new career: knowledge and confidence. I’m thankful that I got both from my training experience at Forte Knowledge. While I was taking classes there, the staff became my close friends and supported me from admission to graduation, then to finding a job. I'm so happy that I've started my own career in QA Testing!

Viktoriia Stefanska · Motorola Mobility LLC