COMMON POWERUp 2024

Quality Assurance in software development is known to be an important factor for IT teams and goals. Regardless if testing is done by developers or testers it is crucial. We will talk about concepts and practices defined as the foundation of testing by ISTQB methodology. This will covering topics such as defects and ramifications, how testing is part of the larger quality assurance model, the definitions of error, defect, fault, and failure. We will discuss the difference between debugging and testing, the objectives of testing, and how testing changes at different parts of development and in different development lifecycles.

Learning Objectives:
Describe how a defect in software can cause harm to a company. Distinguish between the cause of a defect and its effects. Give reasons why testing is necessary by giving examples. Describe why testing is part of quality assurance with examples of how testing contributes to higher quality. Explain and compare the terms error, defect, fault, failure, and the corresponding terms mistake and bug. Recall the common objectives of testing.

Iterative development models are being used more frequently. We will discuss the concepts of Rapid Application Development focusing on agile methodology. Topics include the manifesto and how it relates to teams and practices. From there we will explore testing advantages and challenges and how to be productive. Test automation is a core concept in most agile implementations so we will cover how tools apply and can be used.

Learning Objectives:
Learning Objectives:
Understand Iterative Life Cycles
Define incremental development models and Iterative development model
Understand Basic Agile concepts and the manifesto
Determine the best types of testing for specific applications in a RAD environment

This session is a deep dive into the creation of tests:
• Covering scope, approach, resources, schedule of activities, features, tasks.
• Determine entry and exit criteria and the rational for what is decided upon as well as establishing bi-directional functionality.
• Organize input values, execution preconditions, expected results, and post conditions into test cases.
• Isolate what items or components of the system can be verified by a case.
• Write cases that are repeatable, verifiable, and traceable back to the requirements, quality risk, etc.
• Transform the above into executable tests that scale to all levels of testing infrastructure

Learning Objectives:
1) Take foundational or informal knowledge of testing and improve it procedurally for optimal results.
2) Organize the components of proper testing into a viable plan

Do you have monolithic programs that you have to start breaking up into manageable pieces? Have you been tasked to start unit testing and don’t know where to start? This session is meant for you.

Learning Objectives:
We will work through the benefits to modernizing your code and why you want to adopt unit testing.
We will work through breaking apart monolithic programs and how to write their respective unit tests.
We will discuss some best practices in unit testing and how you can take some of those best practices and apply them to your everyday development processes.

If you’ve ever been asked to create tests for an application that has been in production for years, but has few to no documented requirements, this session will give you a methodology for approaching the challenge.

Learning Objectives:

• What needs to be in your test environment
• What data drives the application logic
• How to leverage Tribal Knowledge for requirements
• Measuring your test coverage
• What resources are available to provide application understanding