This is chapter 2 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 3 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - The Technical Test Analyst Tasks in Risk Based TestingNeeraj Kumar Singh
Â
This is chapter 1 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 6 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
Â
The document discusses quality characteristics for technical testing, focusing on reliability testing. It provides definitions and explanations of reliability sub-characteristics like maturity, fault tolerance, and recoverability. It describes approaches to measuring software maturity and reliability over time. Types of reliability tests discussed include fault tolerance testing, recoverability (failover and backup/restore) testing, and availability testing. General guidance is provided on planning and specifying reliability tests, noting the need for production-like environments and long test durations to obtain statistically significant results.
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation, Risk of Test Automation, Selecting a tool for Organization, Pilot Project, Success factor for using a tool
This is chapter 2 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 2 - Testing Throughout the Development LifeCycleNeeraj Kumar Singh
Â
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made.
This is chapter 3 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - The Technical Test Analyst Tasks in Risk Based TestingNeeraj Kumar Singh
Â
This is chapter 1 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 6 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
Â
The document discusses quality characteristics for technical testing, focusing on reliability testing. It provides definitions and explanations of reliability sub-characteristics like maturity, fault tolerance, and recoverability. It describes approaches to measuring software maturity and reliability over time. Types of reliability tests discussed include fault tolerance testing, recoverability (failover and backup/restore) testing, and availability testing. General guidance is provided on planning and specifying reliability tests, noting the need for production-like environments and long test durations to obtain statistically significant results.
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation, Risk of Test Automation, Selecting a tool for Organization, Pilot Project, Success factor for using a tool
This is chapter 2 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 2 - Testing Throughout the Development LifeCycleNeeraj Kumar Singh
Â
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made.
This is the chapter 3 of ISTQB Agile Tester Extension certification. This presentation helps aspirants understand and prepare content of certification.
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
This is chapter 1 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
This is chapter 2 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
The document summarizes the key activities in the software testing process according to ISTQB, including test planning, monitoring and control, analysis, design, implementation, execution, evaluating exit criteria and reporting, and test closure activities. It provides details on each activity, such as the objectives of test planning, factors to consider for test analysis, and outputs that should be captured during test closure.
This is chapter 3 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Mobile Application Platforms, Tools and EnvironmentNeeraj Kumar Singh
Â
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
The document provides information about preparing for the ISTQB Foundation Level Examination. It discusses that ISTQB is an international software testing certification organization. It operates the ISTQB Certified Tester certification which is based on an established syllabus. The syllabus covers 6 chapters on fundamentals of testing, testing throughout the software life cycle, static techniques, test design techniques, test management, and tool support for testing. The exam has 40 multiple choice questions to be completed in 90 minutes, with a passing score of 65% or 26 correct answers. It provides tips for preparation such as allowing enough time, studying the complete syllabus, taking sample tests, and carefully reading questions and answers.
This is chapter 2 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 3 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is the chapter 5 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
This document discusses software engineering and software testing. Software engineering is concerned with developing large software through applying engineering principles. The challenge is to produce high quality software within budget and schedule constraints. Software testing is the process of finding errors in software and involves both manual and automated testing. Different types of testing include unit, integration, system, and acceptance testing. The goal of testing is to uncover defects early and reduce costs.
This is the chapter 8 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
White-box Testing: When Quality Really MattersTechWell
Â
Jamie Mitchell explores perhaps the most underused test technique in our arsenalâwhite-box testing. Also known as structural testing, white-box requires some programming expertise, access to the code, and an analysis tool. If you only employ black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Not good! Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage your project requires? Jamie describes the levels of code coverage that the business and your customers may needâfrom statement coverage to modified condition/decision coverage. Leading you through examples of pseudocode, Jamie explains when you should strive to achieve different code coverage target levels. Even if you have no personal programming experience, understanding structural testing will make you a better tester. So, join Jamie for some code-diving!
This is a free module from my course ISTQB CTAL Technical Test Analyst revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
This is the chapter 3 of ISTQB Agile Tester Extension certification. This presentation helps aspirants understand and prepare content of certification.
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
This is chapter 1 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
This is chapter 2 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
The document summarizes the key activities in the software testing process according to ISTQB, including test planning, monitoring and control, analysis, design, implementation, execution, evaluating exit criteria and reporting, and test closure activities. It provides details on each activity, such as the objectives of test planning, factors to consider for test analysis, and outputs that should be captured during test closure.
This is chapter 3 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Mobile Application Platforms, Tools and EnvironmentNeeraj Kumar Singh
Â
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
The document provides information about preparing for the ISTQB Foundation Level Examination. It discusses that ISTQB is an international software testing certification organization. It operates the ISTQB Certified Tester certification which is based on an established syllabus. The syllabus covers 6 chapters on fundamentals of testing, testing throughout the software life cycle, static techniques, test design techniques, test management, and tool support for testing. The exam has 40 multiple choice questions to be completed in 90 minutes, with a passing score of 65% or 26 correct answers. It provides tips for preparation such as allowing enough time, studying the complete syllabus, taking sample tests, and carefully reading questions and answers.
This is chapter 2 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 3 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is the chapter 5 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
This document discusses software engineering and software testing. Software engineering is concerned with developing large software through applying engineering principles. The challenge is to produce high quality software within budget and schedule constraints. Software testing is the process of finding errors in software and involves both manual and automated testing. Different types of testing include unit, integration, system, and acceptance testing. The goal of testing is to uncover defects early and reduce costs.
This is the chapter 8 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
White-box Testing: When Quality Really MattersTechWell
Â
Jamie Mitchell explores perhaps the most underused test technique in our arsenalâwhite-box testing. Also known as structural testing, white-box requires some programming expertise, access to the code, and an analysis tool. If you only employ black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Not good! Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage your project requires? Jamie describes the levels of code coverage that the business and your customers may needâfrom statement coverage to modified condition/decision coverage. Leading you through examples of pseudocode, Jamie explains when you should strive to achieve different code coverage target levels. Even if you have no personal programming experience, understanding structural testing will make you a better tester. So, join Jamie for some code-diving!
This is a free module from my course ISTQB CTAL Technical Test Analyst revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
Test design techniques: Structured and Experienced-based techniquesKhuong Nguyen
Â
This document discusses different types of software testing techniques, including structured-based techniques like cyclomatic complexity and statement/decision coverage, as well as experience-based techniques like error guessing and exploratory testing. It explains how to calculate cyclomatic complexity and coverage percentages. Choosing the appropriate testing technique depends on factors like system type, standards, requirements, risk level, documentation, tester knowledge, time and budget. Testing usually involves combining different techniques.
Structural Testing: When Quality Really MattersTechWell
Â
Jamie Mitchell explores an underused and often forgotten test techniqueâwhite-box testing. Also known as structural testing, this technique requires some programming expertise and access to the code. Using only black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Are you comfortable with that? For mission-critical systems, such low test code coverage is clearly insufficient. Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage that your project requires? Jamie describes the levels of code coverage that the business and your customers may needâfrom statement coverage to modified condition/decision coverage. He explains when you should strive to achieve different code coverage target levels and leads you through examples of pseudocode. Even if you have no personal programming experience, understanding structural testing will make you a better tester. So, join Jamie in this code-diving session.
The document describes the testing life cycle process which includes test plan preparation, test case design, test execution and log preparation, defect tracking, and test report preparation. It then provides details about each step of the testing life cycle process such as how to prepare test plans, design test cases, execute tests and log results, track defects, and prepare test reports.
The document describes the testing life cycle process which includes test plan preparation, test case design, test execution and log preparation, defect tracking, and test report preparation. It then provides details about each step of the testing life cycle including preparing test plans, designing test cases, executing tests, tracking defects, and generating test reports.
This document discusses various static and dynamic testing techniques. It explains that static testing is done manually without executing code, such as reviews and inspections. Dynamic testing requires executing the code using techniques like unit testing. Black box techniques like equivalence partitioning, boundary value analysis, decision tables, and state transition testing are covered, along with an example for each. White box techniques focus on internal code structure and test coverage metrics. The document provides details on different testing techniques for testers to design effective test cases.
Best Way to Prepare for the ISTQB Technical Test Analyst (CTAL-TTA) Certifica...Meghna Arora
Â
Start Here---> http://bit.ly/2WtdgTj <---Get complete detail on CTAL-TTA exam guide to crack Technical Test Analyst. You can collect all information on CTAL-TTA tutorial, practice test, books, study material, exam questions, and syllabus. Firm your knowledge on Technical Test Analyst and get ready to crack CTAL-TTA certification. Explore all information on CTAL-TTA exam with the number of questions, passing percentage, and time duration to complete the test.
The document discusses various software testing techniques including:
- Unit testing techniques like white box testing, gray box testing, and equivalence partitioning
- Integration testing techniques like boundary value analysis and error guessing
- The iterative process of test-driven development where tests are written before implementing features
It provides an example of using these techniques to test a TrafficSignal class through a series of test methods.
This document outlines the steps in a Six Sigma DMAIC process improvement project. It includes defining critical metrics, measuring current performance, analyzing processes, improving processes through pilot tests, and controlling ongoing performance. Key steps are defining customer needs, measuring baseline performance, determining critical factors, piloting solutions, creating control systems, and finalizing documentation.
This document outlines the steps in a Six Sigma DMAIC process improvement project. It includes defining the problem and critical metrics, measuring current performance, analyzing processes and measurements, improving the processes, and controlling future performance. Key steps are defining critical metrics, establishing baselines, determining root causes, piloting solutions, creating control systems, and finalizing documentation.
1. Download and run the installer executable on each workstation to install the Test Delivery Client software.
2. Install any required ancillary applications like Java and Adobe Air.
3. Uninstall any existing Test Delivery Client software.
4. Configure the proxy settings file if a proxy is used.
5. Copy the test content files to the installation folder.
6. Launch the Test Delivery Client to verify a successful installation.
20050314 specification based regression test selection with risk analysisWill Shen
Â
This document describes a specification-based regression test selection technique with risk analysis. It selects targeted tests to cover changes in code or specifications, and safety tests directed by risk analysis. Safety tests are chosen using a risk exposure model factoring probability and cost of faults. Scenarios simulating user profiles are also selected based on their risk exposure covering critical test cases. The approach was evaluated on an IBM project and found effective, cost-efficient, and sensitive to risk. Future work includes determining when to stop testing and implementing the approach in a production environment.
The document discusses different types of software testing including white box testing, black box testing, integration testing, system and acceptance testing, and regression testing. It describes various techniques for each type such as statement coverage for white box testing and requirements-based testing for black box testing. The goal of testing is to find errors, check requirements, and evaluate properties like reliability, performance, and security.
The document contains 40 multiple choice questions related to software testing concepts and terminology. Some of the topics covered in the questions include types of testing (e.g. integration testing, system testing), test design techniques (e.g. boundary value analysis), test management processes (e.g. test estimation, test monitoring), and software quality attributes (e.g. reliability). The questions are from an ISTQB certification sample exam and include a answer key indicating the correct response for each question.
Graham et.al, 2008, Foundations of Software Testing ISTQB Certification. Chap...Muhammad Jazman
Â
QA is taken from following textbook:
Foundations of Software Testing(Updated)
ISTQB Certification
by Dorothy Graham, Erik Van Veenendaal, Isabel Evans, Rex Black, Graham Isabel
Paperback, 258 Pages, Published 2008 by Cengage Learning Emea
ISBN-13: 978-1-84480-989-9, ISBN: 1-84480-989-7
An Automated Tool for MC/DC Test Data GenerationAriful Haque
Â
Structural testing is often the most common sought criteria for exercising aspects of control flow (i.e. such as
statement, branch and path coverage). In many cases, criteria based on statement, decision and path coverage appears
sufficiently effective for testing (in terms of selecting the appropriate test cases for testing consideration) the various parts of the software implementation. In other cases involving complex predicates, criteria based on statement, branch, and path coverage appear problematic owing to the problem of masking (where one variable is âmaskingâ the effects of other variables). Addressing this issue, this paper discusses the design and implementation of an automatic test data generation called MC/DC GEN for structural testing based on Multiple Condition/Decision Coverage (MC/DC). In doing so, this paper also highlights the possible adoption of MC/DC GEN for practical use.
A Test Analysis Method for Black Box Testing Using AUT and Fault Knowledge.Tsuyoshi Yumoto
Â
With a rapid increase in size and complexity of software today, the scope of software testing is also expanding. The efficiency of software testing needs to be improved in order to ensure the appropriate delivery deadline and cost of software development. For improving efficiency of software testing, the test needs to be designed in a way that the number of test cases is sufficient and appropriate in quantity. Test analysis is the activity to refine Application Under Test (AUT) into proper size that test design techniques can be applied to. It is for designing the test properly. However, the classification for proper size depends on individualâs own judgments. This paper proposes a test analysis method for the black box testing using a test category that is the classification based on fault and AUT knowledge.
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Common Test Types and Test Process for Mobile ApplicationsNeeraj Kumar Singh
Â
This is chapter 3 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - Mobile World - Business and Technology DriversNeeraj Kumar Singh
Â
This is chapter 1 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is a Sample Question Paper of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is the answer to Sample Questions of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
ISTQB Performance Tester Certification Syllabus and Study MaterialNeeraj Kumar Singh
Â
This is Syllabus of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Performance Testing in the Software LifecycleNeeraj Kumar Singh
Â
The document discusses performance testing activities across different software development lifecycles. It describes how performance testing should be conducted iteratively throughout sequential development models, with testing at each stage from concept to acceptance. For iterative models, performance testing is also iterative and can be part of continuous integration. Specific activities discussed include test planning, monitoring, analysis, design, implementation, execution and completion. Performance risks are also discussed for different architectures.
This is chapter 7 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 6 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 4 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
ISTQB Technical Test Analyst Answers to Sample Question PaperNeeraj Kumar Singh
Â
Here are the answers and justification for the sample question paper for ISTQB Advance Technical Test Analyst for certification preparation. This is a standard paper from ISTQB.
This document contains a sample exam for the ISTQB Advanced Level Technical Test Analyst certification. It includes 45 multiple choice questions on topics such as test coverage types, risk analysis, and defect targeting. The questions aim to assess knowledge related to test design, test analysis, and test management. It also provides the exam structure and responsibilities of the exam working group as defined by ISTQB.
ISTQB Advance level syllabus 2019 Technical Test AnalystNeeraj Kumar Singh
Â
Technical Test Analysts contribute to risk-based testing in the following ways:
1) They help identify technical product risks such as those related to security, reliability, and performance, drawing on their technical expertise.
2) They assess identified risks by estimating their likelihood and impact.
3) They help mitigate risks by designing and executing technical tests that reduce the risks to an acceptable level.
The document is a sample exam for the ISTQB Agile Technical Tester (ATT) Advanced Level certification. It includes 40 multiple choice questions testing knowledge related to agile testing practices and techniques. The questions cover topics such as test automation, test-driven development, behavior-driven development, risk-based testing, and continuous integration. The correct answers for each question are provided along with an explanation of the rationale behind each answer. The sample exam is intended to help ISTQB Member Boards in writing questions for the actual ATT Advanced Level certification exam.
Fueling AI with Great Data with Airbyte WebinarZilliz
Â
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Â
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Â
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
Â
An English đŹđ§ translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech đšđż version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Â
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Â
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
Weâll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Â
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Â
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
ââTwitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
â
âFacebook(Meta): https://www.facebook.com/mydbops/
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
Â
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
"Choosing proper type of scaling", Olena SyrotaFwdays
Â
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Northern Engraving | Modern Metal Trim, Nameplates and Appliance PanelsNorthern Engraving
Â
What began over 115 years ago as a supplier of precision gauges to the automotive industry has evolved into being an industry leader in the manufacture of product branding, automotive cockpit trim and decorative appliance trim. Value-added services include in-house Design, Engineering, Program Management, Test Lab and Tool Shops.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
Â
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power gridâs behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
1. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
2. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
3. White Box Test Techniques
Introduction
Each specific technique enables test cases to be derived systematically and focuses on a particular aspect of the
structure to be considered. The techniques provide coverage criteria which have to be measured and associated
with an objective defined by each project or organization.
Achieving full coverage does not mean that the entire set of tests is complete, but rather that the technique being
used no longer suggests any useful tests for the structure under consideration.
The following techniques are considered in this syllabus:
ï” Statement testing
ï” Decision testing
ï” Modified Condition/Decision Coverage (MC/DC) testing
ï” Multiple Condition testing
ï” Basis Path testing
ï” API testing
Neeraj Kumar Singh
4. White Box Test Techniques
Statement Testing
Neeraj Kumar Singh
True
False?
Read A
Read B
If A>B then
Print âA is Biggerâ
Else
Print âB is Biggerâ
End If
Statement Testing or Coverage is a measure of the number of
executable statements in the source code exercised by tests.
Start
End
Branch
Nodes
A,B
A>B
A
B
End If
5. White Box Test Techniques
Statement Testing
True
False?
Read A
Read B
If A>B then
Print âA is Biggerâ
Else
Print âB is Biggerâ
End If
Start
End
A Path is the executable path which reaches the end of
the code starting from the start point.
2
1
A,B
A>B
A
B
End If
6. Example
Statement Testing
Neeraj Kumar Singh
T
IF sufficient water THEN
Boil water
Add tea
Show message âmilk?â
IF milk = yes THEN
Show message âlow fat?â
IF low fat = yes THEN
Add low fat milk
ELSE
Add normal milk
ENDIF
ENDIF
Show message âsugar?â
IF sugar = yes THEN
Add sugar
ENDIF
Stir
Wait 3 minutes
Show message âplease take your teaâ
ELSE
Show message âplease fill up waterâ
ENDIF
Sufficient
Water
Boil
Water
Add
Tea
Milk?
Milk=Yes
Low
Fat?
Low Fat
= Yes
Low fat
Milk
Normal
Milk
End If
Sugar?
Sugar
=Yes
End If
Add
Sugar?
End If
Please fill
up water
Stir, wait
Please take your tea.
End If
F
F
T
T
F
F
T
7. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
8. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
9. White Box Test Techniques
Decision Testing
Neeraj Kumar Singh
True
False?
Read A
Read B
If A>B then
Print âA is Biggerâ
Else
Print âB is Biggerâ
End If
Decision Testing or Coverage is a measure of the number of executable
decisions in the source code exercised by tests.
Start
End
Branch/
Decisions
Nodes/
Statements
A,B
A>B
A
B
End If
10. White Box Test Techniques
Decision Testing
True
False?
Read A
Read B
If A>B then
Print âA is Biggerâ
Else
Print âB is Biggerâ
End If
Start
End
A Path is the executable path which reaches the end of
the code starting from the start point.
2
1
A,B
A>B
A
B
End If
11. Example
Decision Testing
Neeraj Kumar Singh
TStatement P
IF A THEN
IF B THEN
Statement Q
ELSE
Statement R
ENDIF
ELSE
Statement S
IF C THEN
Statement T
ELSE
Statement U
ENDIF
ENDIF
Statement V
How many test cases would you design to achieve 100%
decision coverage?
A
STMT P
END IF
F
F F
B
STMT Q
T
STMT R
STMT S
C
T
STMT T
STMT U
END IF
END IF
STMT V
Min TC for 100% DC = 4
#TIP â No of If +1
12. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
13. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
14. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Compared to Decision testing, which considers the entire decision as a whole and evaluates the TRUE and FALSE
outcomes in separate test cases, MC/DC testing considers how a decision is made when it includes multiple
conditions
Each decision predicate is made up of one or more simple atomic conditions, each of which evaluates to a discrete
Boolean value. These are logically combined to determine the final outcome of the decision. This technique checks
that each of the atomic conditions independently and correctly affects the outcome of the overall decision.
This technique provides a stronger level of coverage than statement and decision coverage when there are
decisions containing multiple conditions.
Assuming N unique, independent atomic conditions, MC/DC can usually be achieved with N+1 unique test cases.
MC/DC requires pairs of test cases that show a single atomic condition can independently affect the result of a
decision.
Neeraj Kumar Singh
15. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
Min TC for 100% MC/DC Coverage is N+1
Where N is no of conditions
16. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
17. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
18. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
19. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
A = {1,5} {2,6} {3,7}
B = {2,4}
C = {3,4}
20. White Box Test Techniques
Modified Condition/Decision Coverage(MC/DC)
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
Min TC for 100% MC/DC Coverage is N+1
Where N is no of conditions
A = {1,5} {2,6} {3,7}
B = {2,4}
C = {3,4}
TC = {2,3,4,6}
21. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
22. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
23. White Box Test Techniques
Multiple Condition Testing
In rare instances, it might be required to test all possible combinations of atomic conditions that a decision may
contain. This exhaustive level of testing is called multiple condition testing.
The number of required tests is dependent on the number of atomic conditions in the decision statement and can
be determined by calculating 2N where N is the number of uncoupled atomic conditions.
Coverage is measured as the number of unique condition combinations executed by the tests divided by the total
number of condition combinations in the test object, normally expressed as a percentage.
The number of test cases can be derived directly from a truth table containing all of the atomic conditions, this
level of coverage can easily be determined. However, the sheer number of test cases required makes MC/DC
coverage more feasible for most situations.
Neeraj Kumar Singh
24. White Box Test Techniques
Multiple Condition Testing
Tests A B C Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C))
(A AND (B OR C))
Min TC for 100% MCT Coverage is 2N
Where N is no of conditions
25. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
26. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
27. White Box Test Techniques
Basis Path Testing
Path testing in general consists of identifying paths through the code and then creating tests to cover them.
Conceptually, it would be useful to test every unique path through the system. In any non-trivial system, however,
the number of test cases could become excessively large due to the nature of looping structures.
The technique is applied by the following steps:
1. Create a control flow graph for a given specification item (e.g., code or functional design specification). Note
that this may also be the first step in performing control flow analysis.
2. Select a baseline path through the code (not an exception path). This baseline path should be the most
important path to test â risk could be used to make this judgment.
3. Generate the second path by changing the outcome of the first decision on the path, while keeping the
maximum number of decision outcomes the same as the baseline path.
4. Generate the third path by again starting with the baseline path and changing the outcome of the second
decision on the path. When multiway decisions are encountered (e.g., a case statement), each outcome of the
decision should be exercised before moving on to the next decision.
5. Generate further paths by changing each of the outcomes on the baseline path. When new decisions are
encountered, the most important outcome should be followed first.
6. Once all the decision outcomes on the baseline path have been covered, apply the same approach to
subsequent paths until all the decision outcomes in the specification item have been exercised.
Neeraj Kumar Singh
28. White Box Test Techniques
Basis Path Testing
Tests Paper Pen Pencil Outcome
1 T T T T
2 T T F T
3 T F T T
4 T F F F
5 F T T F
6 F T F F
7 F F T F
8 F F F F
Neeraj Kumar Singh
(A && (B | C)) = Write
(Paper AND (Pen OR Pencil))
29. Neeraj Kumar Singh
White Box Test Techniques
Basis Path Testing
TStatement P
IF A THEN
IF B THEN
Statement Q
ELSE
Statement R
ENDIF
ELSE
Statement S
IF C THEN
Statement T
ELSE
Statement U
ENDIF
ENDIF
Statement V
A
STMT P
END IF
F
F F
B
STMT Q
T
STMT R
STMT S
C
T
STMT T
STMT U
END IF
END IF
STMT V
30. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
31. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
32. White Box Test Techniques
API Testing
An Application Programming Interface (API) is code which enables communication between different processes,
programs and/or systems. APIs are often utilized in a client/server relationship where one process supplies some
kind of functionality to other processes.
API Testing is a type of testing rather than a technique. In certain respects, API testing is quite similar to testing a
graphical user interface (GUI). The focus is on the evaluation of input values and returned data.
Negative testing is often crucial when dealing with APIs. Programmers who use APIs to access services external to
their own code may try to use API interfaces in ways for which they were not intended. That means that robust
error handling is essential to avoid incorrect operation.
Combinatorial testing of many different interfaces may be required because APIs are often used in conjunction
with other APIs, and because a single interface may contain several parameters, where values of these may be
combined in many ways.
APIs frequently are loosely coupled, resulting in the very real possibility of lost transactions or timing glitches. This
necessitates thorough testing of the recovery and retry mechanisms. An organization that provides an API interface
must ensure that all services have a very high availability; this often requires strict reliability testing by the API
publisher as well as infrastructure support.
Neeraj Kumar Singh
33. White Box Test Techniques
API Testing
Applicability
API testing is becoming more important for testing systems of systems as the individual systems become distributed or
use remote processing as a way of off-loading some work to other processors. Examples include:
ï” Operating systems calls
ï” Service-oriented architectures (SOA)
ï” Remote procedure calls (RPC)
ï” Web services
Software containerization results in the division of a software program into several containers which communicate
with each other using mechanisms such as those listed above. API testing should also target these interfaces.
Limitations/Difficulties
Testing an API directly usually requires a Technical Test Analyst to use specialized tools. Because there is typically no
direct graphical interface associated with an API, tools may be required to setup the initial environment, marshal the
data, invoke the API, and determine the result.
Neeraj Kumar Singh
34. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
35. White Box Test Techniques
Contents
2.1 Introduction
2.2 Statement Testing
2.3 Decision Testing
2.4 Modified Condition/Decision Coverage
(MC/DC) Testing
2.5 Multiple Condition Testing
2.6 Basis Path Testing
2.7 API Testing
2.8 Selecting a White-box Test Technique
Neeraj Kumar Singh
36. White Box Test Techniques
Selecting a White-box Test Technique
The context of the system under test will have an impact on its product risk and criticality levels ( see below).
These factors influence the required coverage metric (and hence the white-box test technique to use) and the
depth of coverage to be achieved. In general, the more critical the system and the higher the product risk level,
the more rigorous the coverage requirements and the higher the need for time and resources to achieve the
desired coverage.
Sometimes the required coverage metric may be derived from applicable standards that apply to the software
system. For example, if the software were to be used in an airborne environment, it may be required to conform
to standard DO-178C (in Europe, ED-12C.)
This standard contains the following five failure conditions:
A. Catastrophic: failure may cause lack of critical function needed to safely fly or land the plane
B. Hazardous: failure may have a large negative impact on safety or performance efficiency
C. Major: failure is significant, but less serious than A or B
D. Minor: failure is noticeable, but with less impact than C
E. No effect: failure has no impact on safety
Neeraj Kumar Singh
37. White Box Test Techniques
Selecting a White-box Test Technique
If the software system is categorized as level A, it must be tested to 100% MC/DC coverage. If it is level B, it must
be tested to 100% decision level coverage and MC/DC is optional. Level C requires 100% statement coverage at a
minimum.
Likewise, [IEC61508] is an international standard for the functional safety of programmable, electronic, safety-
related systems. This standard has been adapted in many different areas, including automotive, rail,
manufacturing, nuclear power plants, and machinery. Criticality is defined using a scale of Safety Integrity Levels
(SIL) where SIL1 is the least critical and SIL4 the most critical. The standard gives recommendations for test
coverage, as shown in the following table (note that the exact definitions for each SIL and for the meaning of
ârecommendedâ and âhighly recommendedâ is defined in the standard).
Neeraj Kumar Singh
38. White Box Test Techniques
1 TTAâs Task in
Risk Based Testing
2 White Box Test
Techniques
3 Analytical
Techniques
Software Testing - ISTQB Advance
Technical Test Analyst Exam Preparation
Chapter 2
Neeraj Kumar Singh
4 Dynamic Analysis 5 Reviews
6 Test Tools &
Automation
39. White Box Test Techniques
Sample Questions Pattern
Neeraj Kumar Singh
Source : www.istqb.org
Chapter 2 Questions
Distribution
K-Level Number of Questions per
LO(Group)
Summary
TTA-2.2 K3 1
There is a total of questions required
for chapter 2
K3 = 6
K4 = 2
TTA-2.3 K3 1
TTA-2.4 K3 1
TTA-2.5 K3 1
TTA-2.6 K3 1
TTA-2.7 K3 1
TTA-2.8 K4 2
40. White Box Test Techniques
Sample Questions
1. You are testing a photo-enforcement system for traffic control in an intersection. It has been determined that a photo
should be taken if the signal light is red (RED) or the car is speeding (SPEED) and if the front wheels of the car are over
the line marking the beginning of the intersection (WHEELS).
Consider these sets of test values:
Assume the logic in the code is as follows:
IF ((RED OR SPEED) AND WHEELS) THEN
TAKE THE PHOTO
ELSE
DO NOT TAKE THE PHOTO
Given this information, which sets of values provides the minimum tests to achieve 100% modified condition/decision
coverage?
Select ONE option.
Answer Set
a. 1, 3, and 8.
b. 2 and 8.
c. 3, 4, 5, and 7.
d. 1, 5, 7, and 8.
Neeraj Kumar Singh
1. RED + SPEED + WHEELS
2. RED + SPEED + not WHEELS
3. RED + not SPEED + WHEELS
4. RED + not SPEED + not WHEELS
5. not RED + SPEED + WHEELS
6. not RED + SPEED + not WHEELS
7. not RED + not SPEED + WHEELS
8. not RED + not SPEED + not WHEELS
41. White Box Test Techniques
Sample Questions
2. You are testing a photo-enforcement system for traffic control in an intersection. It has been determined that a photo
should be taken if the signal light is red (RED) or the car is speeding (SPEED) and if the front wheels of the car are over
the line marking the beginning of the intersection (WHEELS).
Consider these sets of test values:
Assume the logic in the code is as follows:
IF ((RED OR SPEED) AND WHEELS) THEN
TAKE THE PHOTO
ELSE
DO NOT TAKE THE PHOTO
Given this information, which sets of values provide the minimum tests to achieve 100% multiple condition coverage?
Select ONE option.
Answer Set
a. All the sets are needed.
b. 3, 4, 5, and 7.
c. 1, 3, and 8.
d. 1, 5, 7, and 8.
Neeraj Kumar Singh
1. RED + SPEED + WHEELS
2. RED + SPEED + not WHEELS
3. RED + not SPEED + WHEELS
4. RED + not SPEED + not WHEELS
5. not RED + SPEED + WHEELS
6. not RED + SPEED + not WHEELS
7. not RED + not SPEED + WHEELS
8. not RED + not SPEED + not WHEELS
42. White Box Test Techniques
Sample Questions
3. You are testing a photo-enforcement system for traffic control in an intersection. It has been determined that a photo
should be taken if the signal light is red (RED) or the car is speeding (SPEED) and if the front wheels of the car are over
the line marking the beginning of the intersection (WHEELS).
Consider these sets of test values:
Assume the logic in the code is as follows:
IF ((RED OR SPEED) AND WHEELS) THEN
TAKE THE PHOTO
ELSE
DO NOT TAKE THE PHOTO
Given this information, which sets of values provide the minimum tests to achieve full coverage of basis paths?
Select ONE option.
Answer Set
a. 3, 4, 5, 7
b. 2, 3
c. 1, 3, 8
d. 1
Neeraj Kumar Singh
1. RED + SPEED + WHEELS
2. RED + SPEED + not WHEELS
3. RED + not SPEED + WHEELS
4. RED + not SPEED + not WHEELS
5. not RED + SPEED + WHEELS
6. not RED + SPEED + not WHEELS
7. not RED + not SPEED + WHEELS
8. not RED + not SPEED + not WHEELS
43. White Box Test Techniques
Sample Questions
4. Which of the following types of defects are targeted by API testing?
Select TWO options.
Answer Set
a. Loss of transactions.
b. Non-conformance to coding standards.
c. Incorrect data handling.
d. Installation defects.
e. GUI faults.
Neeraj Kumar Singh
44. White Box Test Techniques
Sample Questions
5. You are advising the developers in an agile team on the appropriate test coverage to be achieved in the next
sprint. Three business-critical user stories are on the sprint backlog. Each user story requires that several
sequential actions are performed with some simple error handling routines. Which is the level of test coverage
you would expect to be achieved in the testing of the user stories??
Select ONE option.
Answer Set
a. Decision coverage + Modified Condition/Decision coverage.
b. Decision coverage + Statement coverage.
c. Modified Condition/Decision coverage.
d. Multiple Condition coverage.
Neeraj Kumar Singh