Test Cases Maintaining & Documenting
•Download as PPS, PDF•
6 likes•4,491 views
The document discusses test case design and components. It defines a test case as a set of test inputs, execution conditions and expected results to exercise a program path or verify a requirement. Test cases have three main components - inputs, outputs and execution order. The document also discusses advantages of effective test cases such as higher probability of detecting defects and delivering higher quality software. It describes black box and white box testing approaches and provides tips for writing good test cases and prioritizing test cases.
Report
Share
Report
Share
Recommended
Writing Test Cases 20110808
Test cases are used to systematically test software and verify requirements. A test case contains a set of steps, expected results, and actual results. It has a name, description, prerequisites, and test data. Each test case contains multiple test steps that verify a discrete action. Best practices for writing test cases include avoiding jargon, writing steps independently, and focusing on positive scenarios. Test cases are organized into templates with required fields and naming conventions to facilitate management in testing tools.
Best Practices for Test Case Writing
This document provides guidance on how to write effective test cases. It discusses test case components like objectives, preconditions, steps, and expected results. It emphasizes making test cases clear, concise, reusable, and up-to-date to reflect any application changes. The document also highlights techniques like breaking tests into focused subsets and attaching relevant artifacts.
Effective Software Test Case Design Approach
Effective Software Test Case Design Approach highlights typical wrong approaches to software test case design and focuses on an effective methodology in test case design from a collaborative approach.
Through the use of an example requirement/user story, this presentation highlights the "interactions" between the stakeholders, i.e. Product Owner, Developer, and Test Engineer in the development of user story acceptance criteria, details, test scope, and effective, consistent and valid test cases.
Test cases
A test case is a set of conditions or variables under which a tester will determine whether a software system is working correctly. Test cases are often written as test scripts and collected into test suites. Characteristics of good test cases include being simple, clear, concise, complete, non-redundant, and having a reasonable probability of catching errors. Test cases should be developed to verify specific requirements or designs and include both positive and negative cases.
So you think you can write a test case
This document provides guidance on writing effective test cases. It discusses that test cases are documentation that guide testing and serve as a record. Key components of a test case are test steps that provide clear instructions to testers, and expected results that describe how to verify the outcome. The document also outlines best practices like starting test case design after exploring the application, using clear and specific language, and providing supplemental materials like test data sheets to support testing. Maintaining test cases is important as applications evolve, requiring test cases to be revised as needed to continue supporting products.
Writing Test Cases in Agile
The document discusses writing test cases in Agile, including defining a test case, sample test case templates, characteristics of a good test case, typical fields in a test case, different levels of test cases, practical approaches to creating Agile test cases, reasons for writing test cases, pros and cons of writing test cases, and references for further information.
Test Automation Framework Designs
See how Martin Lienhard of Williams-Sanoma builds a test automation framework using Selenium, data-driven tests, and much more!
INTRODUCTION TO ISTQB FOUNDATION LEVEL - CTFL
This Slideshare will give you the basics introduction of the ISTQB Foundation level testing certification.
ISTQB stands for the “International Software Testing Qualifications Board.”
ISTQB Certification is a universally acknowledged programming testing affirmation that is directed online by its Member Boards through a testing Exam Provider.
Recommended
Writing Test Cases 20110808
Test cases are used to systematically test software and verify requirements. A test case contains a set of steps, expected results, and actual results. It has a name, description, prerequisites, and test data. Each test case contains multiple test steps that verify a discrete action. Best practices for writing test cases include avoiding jargon, writing steps independently, and focusing on positive scenarios. Test cases are organized into templates with required fields and naming conventions to facilitate management in testing tools.
Best Practices for Test Case Writing
This document provides guidance on how to write effective test cases. It discusses test case components like objectives, preconditions, steps, and expected results. It emphasizes making test cases clear, concise, reusable, and up-to-date to reflect any application changes. The document also highlights techniques like breaking tests into focused subsets and attaching relevant artifacts.
Effective Software Test Case Design Approach
Effective Software Test Case Design Approach highlights typical wrong approaches to software test case design and focuses on an effective methodology in test case design from a collaborative approach.
Through the use of an example requirement/user story, this presentation highlights the "interactions" between the stakeholders, i.e. Product Owner, Developer, and Test Engineer in the development of user story acceptance criteria, details, test scope, and effective, consistent and valid test cases.
Test cases
A test case is a set of conditions or variables under which a tester will determine whether a software system is working correctly. Test cases are often written as test scripts and collected into test suites. Characteristics of good test cases include being simple, clear, concise, complete, non-redundant, and having a reasonable probability of catching errors. Test cases should be developed to verify specific requirements or designs and include both positive and negative cases.
So you think you can write a test case
This document provides guidance on writing effective test cases. It discusses that test cases are documentation that guide testing and serve as a record. Key components of a test case are test steps that provide clear instructions to testers, and expected results that describe how to verify the outcome. The document also outlines best practices like starting test case design after exploring the application, using clear and specific language, and providing supplemental materials like test data sheets to support testing. Maintaining test cases is important as applications evolve, requiring test cases to be revised as needed to continue supporting products.
Writing Test Cases in Agile
The document discusses writing test cases in Agile, including defining a test case, sample test case templates, characteristics of a good test case, typical fields in a test case, different levels of test cases, practical approaches to creating Agile test cases, reasons for writing test cases, pros and cons of writing test cases, and references for further information.
Test Automation Framework Designs
See how Martin Lienhard of Williams-Sanoma builds a test automation framework using Selenium, data-driven tests, and much more!
INTRODUCTION TO ISTQB FOUNDATION LEVEL - CTFL
This Slideshare will give you the basics introduction of the ISTQB Foundation level testing certification.
ISTQB stands for the “International Software Testing Qualifications Board.”
ISTQB Certification is a universally acknowledged programming testing affirmation that is directed online by its Member Boards through a testing Exam Provider.
Test cases
The document discusses test case structure and specifications. It defines a test case as a set of inputs, expected results, and execution conditions used to test a specific program path or requirement. A test case specification is a document that specifies test cases by outlining objectives, inputs, test actions, expected results, and preconditions. It also provides guidelines for writing effective test cases, such as keeping them short, using simple language, and providing test data and notes when possible. The overall goal is to write test cases early based on design to allow for early bug detection and efficient testing once code is completed.
Test case writing
Test cases are documents that contain test data, preconditions, test steps, expected results, and postconditions to verify a specific requirement. They provide a starting point for test execution and leave the system in a defined state. Good test cases are accurate, economical, traceable, repeatable, reusable, simple, objective, relevant, avoid duplication and dependency. Test cases should be written based on requirements documents and cover both positive and negative scenarios using clear language. An ideal test case includes an ID, use case ID, test objective, preconditions, test data, test steps, expected results, actual results, cycle, date, tester, status, severity, and resolution status.
Test Process
The document discusses various aspects of the software testing process including verification and validation strategies, test phases, metrics, configuration management, test development, and defect tracking. It provides details on unit testing, integration testing, system testing, and other test phases. Metrics covered include functional coverage, software maturity, and reliability. Configuration management and defect tracking processes are also summarized.
Test Strategy
Presented on Poznań University of Technology where I had a lecture for students how to choose test approach.
Best practices for test case creation & maintenance
With effective test case writing, companies can standardise the testing process & validate the testing coverage of the application.
Manual testing
Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts related to manual testing including software quality assurance, verification, validation, software life cycles, testing techniques like black box testing and white box testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing. It provides brief definitions and purposes of these concepts.
Test Case, Use Case and Test Scenario
It will help to know about test cases, test scenario and defference between them.
It will also help you to find in what format test cases are written.
Introduction & Manual Testing
The document discusses various software development life cycle models and testing methodologies. It introduces the waterfall model, prototyping model, rapid application development model, spiral model, and component assembly model. It then covers testing fundamentals, test case design, white box and black box testing techniques, and the relationships between quality assurance, quality control, verification and validation.
Test cases for effective testing - part 1
The document discusses test case components and approaches for writing test cases. It provides guidelines for writing test cases such as covering all requirements, prioritizing test cases based on importance, using simple steps and validation input data, focusing on common user scenarios, and ensuring each defect has a linked test case. The document also outlines a test case format including an ID, title, summary, preconditions, steps, and expected results.
ISTQB Foundation Level Basic
Testing serves several purposes: finding defects, gaining confidence in quality, and providing information for decision-making. There are seven key principles of testing: testing shows the presence of defects but not their absence; exhaustive testing is impossible; early testing is most effective; defects tend to cluster; tests can become outdated and less effective over time; testing needs to be tailored to the context; and absence of errors in testing does not guarantee absence of errors in operation. Testing involves several processes: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and closure activities. Testing can be done at the component, integration, system, and acceptance levels and through functional, non-functional, structural, and regression techniques.
Software testing
This document provides an introduction to software testing. It defines software testing as a process used to identify correctness, completeness, and quality of computer software. The key points covered include: why software testing is important; who should be involved in testing; when testing should start and stop in the software development lifecycle; the differences between verification and validation; types of errors; types of testing including manual and automation; methods like black box and white box testing; levels of testing from unit to acceptance; and definitions of test plans and test cases.
Test planning
Aliaa delivered a session in the topic of “Test planning” using a new technique of delivering content through games and knowledge sharing instead of instructive technique. The session covered all test planning activities including defining test items, risk assessment techniques, testing strategies, planning for testing resources, testing scheduling, and test deliverables and the final test plan documents.
The session introduced to quality team at ITWorx (June , 2013)
Manual testing concepts course 1
Testing software is conducted to ensure the system meets user needs and requirements. The primary objectives of testing are to verify that the right system was built according to specifications and that it was built correctly. Testing helps instill user confidence, ensures functionality and performance, and identifies any issues where the system does not meet specifications. Different types of testing include unit, integration, system, and user acceptance testing, which are done at various stages of the software development life cycle.
Test Management introduction
The document discusses test management for software quality assurance, including defining test management as organizing and controlling the testing process and artifacts. It covers the phases of test management like planning, authoring, execution, and reporting. Additionally, it discusses challenges in test management, priorities and classifications for testing, and the role and responsibilities of the test manager.
Software Testing 101
A presentation to explain the goals and methods of testing to a variety of colleagues who help with testing on certain projects...
ISTQB Test level, Test type
The document discusses different types of testing throughout the software development lifecycle, including component testing, integration testing, system testing, and acceptance testing. It provides objectives and typical defects found for each type. Component testing focuses on individual components/units and verifies functionality and prevents defects. Integration testing focuses on interfaces and prevents interface defects. System testing verifies full system behavior prevents escapes. Acceptance testing validates system meets requirements. Maintenance testing is also discussed and should be done when changes are made to evaluate success and check for side effects.
Software Testing Life Cycle (STLC) | Software Testing Tutorial | Edureka
*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
SOFTWARE TESTING
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
ISTQB foundation level - day 2
The document provides an agenda for Day 2 of an ISTQB Foundation Level training which includes the following topics: test design techniques like test analysis, test design, equivalence partitioning, boundary value analysis, use case testing and experience-based testing. It also discusses test management topics like test leader and tester roles and responsibilities, test plan vs test strategy, estimation techniques, configuration management, risk based testing, exploratory testing and defect management. The last sections provide overviews of tool support for testing and an exercise on classifying different types of triangles based on side lengths.
Test Automation Frameworks Using Selenium | Edureka
YouTube: https://youtu.be/2idCKxbhXOk
** Test Automation Engineer Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka Live PPT on ‘Test Automation Framework’ will help you learn about what testing frameworks are and how to build one using Selenium. Below topics are covered in this PPT:
Introduction to Automation Testing
Approaches to Test Automation
Test Automation Frameworks
Types of Test Automation Frameworks
Demo: How to build a test automation framework using selenium.
Security Testing Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Scrum Masters: The Full Time Role Conundrum (Brisbane Agile)
The document discusses the role of a Scrum Master and whether it should be a full-time role. It describes Scrum Masters as facilitating the Scrum process and helping the team adhere to practices. It also notes challenges with scaling Scrum in large enterprises and balancing the various duties of a Scrum Master like daily stand-ups, retrospectives, and impediment removal. The document considers whether the role needs to transition over time from full-time to part-time as the team matures.
Agile scrum roles
The document discusses the roles in Scrum, an agile software development methodology. It describes the three main roles: the Scrum Team which develops the software; the Product Owner who prioritizes features and represents customers; and the Scrum Master who leads the team and ensures they follow Scrum practices. The roles work together iteratively with the Scrum Team delivering working software increments each sprint while the Product Owner and Scrum Master provide feedback and guidance.
More Related Content
What's hot
Test cases
The document discusses test case structure and specifications. It defines a test case as a set of inputs, expected results, and execution conditions used to test a specific program path or requirement. A test case specification is a document that specifies test cases by outlining objectives, inputs, test actions, expected results, and preconditions. It also provides guidelines for writing effective test cases, such as keeping them short, using simple language, and providing test data and notes when possible. The overall goal is to write test cases early based on design to allow for early bug detection and efficient testing once code is completed.
Test case writing
Test cases are documents that contain test data, preconditions, test steps, expected results, and postconditions to verify a specific requirement. They provide a starting point for test execution and leave the system in a defined state. Good test cases are accurate, economical, traceable, repeatable, reusable, simple, objective, relevant, avoid duplication and dependency. Test cases should be written based on requirements documents and cover both positive and negative scenarios using clear language. An ideal test case includes an ID, use case ID, test objective, preconditions, test data, test steps, expected results, actual results, cycle, date, tester, status, severity, and resolution status.
Test Process
The document discusses various aspects of the software testing process including verification and validation strategies, test phases, metrics, configuration management, test development, and defect tracking. It provides details on unit testing, integration testing, system testing, and other test phases. Metrics covered include functional coverage, software maturity, and reliability. Configuration management and defect tracking processes are also summarized.
Test Strategy
Presented on Poznań University of Technology where I had a lecture for students how to choose test approach.
Best practices for test case creation & maintenance
With effective test case writing, companies can standardise the testing process & validate the testing coverage of the application.
Manual testing
Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts related to manual testing including software quality assurance, verification, validation, software life cycles, testing techniques like black box testing and white box testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing. It provides brief definitions and purposes of these concepts.
Test Case, Use Case and Test Scenario
It will help to know about test cases, test scenario and defference between them.
It will also help you to find in what format test cases are written.
Introduction & Manual Testing
The document discusses various software development life cycle models and testing methodologies. It introduces the waterfall model, prototyping model, rapid application development model, spiral model, and component assembly model. It then covers testing fundamentals, test case design, white box and black box testing techniques, and the relationships between quality assurance, quality control, verification and validation.
Test cases for effective testing - part 1
The document discusses test case components and approaches for writing test cases. It provides guidelines for writing test cases such as covering all requirements, prioritizing test cases based on importance, using simple steps and validation input data, focusing on common user scenarios, and ensuring each defect has a linked test case. The document also outlines a test case format including an ID, title, summary, preconditions, steps, and expected results.
ISTQB Foundation Level Basic
Testing serves several purposes: finding defects, gaining confidence in quality, and providing information for decision-making. There are seven key principles of testing: testing shows the presence of defects but not their absence; exhaustive testing is impossible; early testing is most effective; defects tend to cluster; tests can become outdated and less effective over time; testing needs to be tailored to the context; and absence of errors in testing does not guarantee absence of errors in operation. Testing involves several processes: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and closure activities. Testing can be done at the component, integration, system, and acceptance levels and through functional, non-functional, structural, and regression techniques.
Software testing
This document provides an introduction to software testing. It defines software testing as a process used to identify correctness, completeness, and quality of computer software. The key points covered include: why software testing is important; who should be involved in testing; when testing should start and stop in the software development lifecycle; the differences between verification and validation; types of errors; types of testing including manual and automation; methods like black box and white box testing; levels of testing from unit to acceptance; and definitions of test plans and test cases.
Test planning
Aliaa delivered a session in the topic of “Test planning” using a new technique of delivering content through games and knowledge sharing instead of instructive technique. The session covered all test planning activities including defining test items, risk assessment techniques, testing strategies, planning for testing resources, testing scheduling, and test deliverables and the final test plan documents.
The session introduced to quality team at ITWorx (June , 2013)
Manual testing concepts course 1
Testing software is conducted to ensure the system meets user needs and requirements. The primary objectives of testing are to verify that the right system was built according to specifications and that it was built correctly. Testing helps instill user confidence, ensures functionality and performance, and identifies any issues where the system does not meet specifications. Different types of testing include unit, integration, system, and user acceptance testing, which are done at various stages of the software development life cycle.
Test Management introduction
The document discusses test management for software quality assurance, including defining test management as organizing and controlling the testing process and artifacts. It covers the phases of test management like planning, authoring, execution, and reporting. Additionally, it discusses challenges in test management, priorities and classifications for testing, and the role and responsibilities of the test manager.
Software Testing 101
A presentation to explain the goals and methods of testing to a variety of colleagues who help with testing on certain projects...
ISTQB Test level, Test type
The document discusses different types of testing throughout the software development lifecycle, including component testing, integration testing, system testing, and acceptance testing. It provides objectives and typical defects found for each type. Component testing focuses on individual components/units and verifies functionality and prevents defects. Integration testing focuses on interfaces and prevents interface defects. System testing verifies full system behavior prevents escapes. Acceptance testing validates system meets requirements. Maintenance testing is also discussed and should be done when changes are made to evaluate success and check for side effects.
Software Testing Life Cycle (STLC) | Software Testing Tutorial | Edureka
*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
SOFTWARE TESTING
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
ISTQB foundation level - day 2
The document provides an agenda for Day 2 of an ISTQB Foundation Level training which includes the following topics: test design techniques like test analysis, test design, equivalence partitioning, boundary value analysis, use case testing and experience-based testing. It also discusses test management topics like test leader and tester roles and responsibilities, test plan vs test strategy, estimation techniques, configuration management, risk based testing, exploratory testing and defect management. The last sections provide overviews of tool support for testing and an exercise on classifying different types of triangles based on side lengths.
Test Automation Frameworks Using Selenium | Edureka
YouTube: https://youtu.be/2idCKxbhXOk
** Test Automation Engineer Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka Live PPT on ‘Test Automation Framework’ will help you learn about what testing frameworks are and how to build one using Selenium. Below topics are covered in this PPT:
Introduction to Automation Testing
Approaches to Test Automation
Test Automation Frameworks
Types of Test Automation Frameworks
Demo: How to build a test automation framework using selenium.
Security Testing Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
What's hot (20)
Best practices for test case creation & maintenance
Best practices for test case creation & maintenance
Software Testing Life Cycle (STLC) | Software Testing Tutorial | Edureka
Software Testing Life Cycle (STLC) | Software Testing Tutorial | Edureka
Test Automation Frameworks Using Selenium | Edureka
Test Automation Frameworks Using Selenium | Edureka
Viewers also liked
Scrum Masters: The Full Time Role Conundrum (Brisbane Agile)
The document discusses the role of a Scrum Master and whether it should be a full-time role. It describes Scrum Masters as facilitating the Scrum process and helping the team adhere to practices. It also notes challenges with scaling Scrum in large enterprises and balancing the various duties of a Scrum Master like daily stand-ups, retrospectives, and impediment removal. The document considers whether the role needs to transition over time from full-time to part-time as the team matures.
Agile scrum roles
The document discusses the roles in Scrum, an agile software development methodology. It describes the three main roles: the Scrum Team which develops the software; the Product Owner who prioritizes features and represents customers; and the Scrum Master who leads the team and ensures they follow Scrum practices. The roles work together iteratively with the Scrum Team delivering working software increments each sprint while the Product Owner and Scrum Master provide feedback and guidance.
What is-requirement-traceability-matrix-and-why-is-it-needed-
A traceability matrix is an archive that compares any two-baseline documents that require a many
to-many relationship to check the fulfillment of the relationship. It is utilized to track the
prerequisites and to check that the present project necessities are met.
Requirements Traceability Matrix Simple
The document discusses requirements traceability matrices, which associate business requirements with use cases and test scripts that validate them. Relationships can be one-to-one, one-to-many, or many-to-one. Unique identifiers are needed for requirements, use cases, and test scripts. Traceability matrices ensure complete testing and provide a basis for test planning. They can be standalone or part of other documents like requirements or test plans.
IOT Firmware: Best Pratices
This document provides best practices for embedded firmware design to make the development process less painful. It recommends using C instead of C++ for firmware programming due to its portability, speed, and clear behavior. State machines should be used everywhere to manage complexity, avoid rare bugs, and make code more testable and reusable. A modular design separates behavior from hardware to enable faster desktop debugging. A hardware abstraction layer isolates hardware interfaces from behavior for portability. On-device debugging should only be used as a last resort due to its slowness compared to desktop debugging.
Building mobile web apps with Mobello
The document introduces the Mobello mobile web app framework. It provides an overview of Mobello, describing it as a JavaScript framework for building richly interactive mobile web apps. It outlines key Mobello concepts like scene controllers, navigators, components for UI elements, theming capabilities, and the Mobello Studio IDE. The document also compares declarative vs programmatic approaches and shows code examples for key framework aspects like scenes, navigation, animation, and component creation.
Bluetooth Smart: Connecting Medical Devices to Smart Phones
Presentation delivered by our Rob Milner to MD&M on connecting medical devices to smart phones in the age of digital health.
APA division# 44 LGBT
This document summarizes research on lesbian, gay, bisexual, and transgender (LGBT) issues from a psychological perspective. It discusses the history of LGBT rights movements and the formation of the APA division on LGBT issues. It then summarizes various psychological studies that have explored potential genetic, hormonal, environmental, and neurological factors that may influence sexual orientation or gender identity. Some key findings discussed are studies linking sexual orientation to prenatal hormone exposure or certain genes and brain structures. The document also summarizes research on bisexuality, transgender identities and experiences, and issues commonly faced by LGBT individuals.
Test Case Naming 02
This document discusses test case naming conventions and strategies. It argues that test cases should be named after the product they test rather than the requirements or project, since those may change over time. The naming should follow a hierarchy that indicates the element being tested, such as the menu, group, icon, and option. This provides context and helps identify what is being tested. Well-named test cases can guide understanding of the system without needing additional documentation. The document provides examples of test case names for Microsoft PowerPoint and Google applications that follow this recommended hierarchical convention.
APA division of Forensic Psychology
Forensic psychology is the intersection between psychology and the justice system. It provides psychological information to facilitate legal decisions. The field grew significantly after World War 2. Forensic psychologists work in clinical, developmental, and social psychology and assist with criminal investigations, profiling, rehabilitation, and analyzing crime trends. They help lawyers with jury selection, consulting, and witness preparation and testify in family, civil, and criminal courts. While criminal psychologists evaluate criminals, forensic psychologists work on all types of court cases, including civil matters not involving criminals. Forensic psychology is an emerging field in Pakistan.
Mobile App Testing
iPhone App Testing
Android App Testing
BlackBerry App Testing
Windows Phone 7 App Testing
iPad App Testing
Traceability matrix
A traceability matrix traces requirements to tests, code, and design specifications. It provides backward traceability from tests to requirements and forward traceability from requirements to tests and code. The matrix links high-level requirements to lower-level tests, design documents, and code files. This allows one to ensure all requirements are tested, identify untested requirements, and determine which tests need updating when requirements change.
Agile vs. waterfall - The fundamentals differences
In this presentation I will review the main differences between waterfall and agile methodology, this presentation is a great place to start if you want to know why more and more companies are using agile as the preferred development methodology.
ATAGTR2017 The way to recover the issue faced in IoT regression Testing
The presentation on The way to recover the issue faced in IoT regression Testing was done during #ATAGTR2017, one of the largest global testing conference. All copyright belongs to the author.
Author and presenter : Anuradha Band
50+ ways to improve tester - programmer relationship
Testers should focus on quality criteria beyond just functionality, write clear bug reports with details and attachments, and respect programmers and their skills. Testers and programmers should collaborate through techniques like heuristics and limitations discussions, asking about code purpose, and finding similar code examples. Building a strong relationship involves serving programmers needs, understanding their schedules, and working together as mentors.
Testing AS A Container - Irfan Ahmad
This document discusses using Docker containers to improve the software testing and delivery process. It outlines challenges with traditional testing approaches like slow deployments and ineffective tests. Docker containers provide a standardized and portable way to run tests quickly by packaging an application and its dependencies. The document demonstrates building test containers, running tests inside containers, and using Docker Compose to test multi-container applications. Best practices like one process per container and shipping images not code are also covered. Overall, Docker containers can help speed up testing, improve test quality, and enable continuous integration and delivery workflows.
IoT testing and quality assurance indicthreads
The document discusses testing for Internet of Things (IoT) software. It begins with an introduction to IoT and describes emerging IoT applications and the typical IoT technology stack. It then discusses challenges in testing IoT software and how the role of quality assurance is changing. The document outlines various areas of IoT testing including connectivity, security, performance, functionality and more. It provides examples of test cases for each area. Finally, it proposes a strategy for effective IoT software testing that emphasizes automation, virtualization, robust backends, and testing at the design stage.
All you need to know about regression testing | David Tzemach
All you need to know about Regression testing| David Tzemach
1. Overview
2. What is “Regression” testing…?
3. When should you use it..?
4. How to implement..?
5. Test Recommendations
6. Considerations when building Regression tests
Android testing
This presentation was presented in Android Only! 2011 conference on June 14th.
With more than 300 different Android devices out on 6 different platform versions, application developers are facing a real nightmare when trying validate that their applications really work on their customers' devices. While fragmentation is a new thing in Android platform, it is not new in software industry and there are several ways to deal with device fragmentation from testing point of view.
This presentation discusses most common approaches to tackle fragmentation from application developer's point of view and explains why testing for device compatibility is a must for any serious Android application developer.
D2D - Device to Device Communication
An overview about the new feature proposed for LTE Release 12 and beyond: Proximity Services (ProSe) / D2D.
It covers the D2D features: Discovery, Communication, Security and also shows some use-cases.
Viewers also liked (20)
Scrum Masters: The Full Time Role Conundrum (Brisbane Agile)
Scrum Masters: The Full Time Role Conundrum (Brisbane Agile)
What is-requirement-traceability-matrix-and-why-is-it-needed-
What is-requirement-traceability-matrix-and-why-is-it-needed-
Bluetooth Smart: Connecting Medical Devices to Smart Phones
Bluetooth Smart: Connecting Medical Devices to Smart Phones
Agile vs. waterfall - The fundamentals differences
Agile vs. waterfall - The fundamentals differences
ATAGTR2017 The way to recover the issue faced in IoT regression Testing
ATAGTR2017 The way to recover the issue faced in IoT regression Testing
50+ ways to improve tester - programmer relationship
50+ ways to improve tester - programmer relationship
All you need to know about regression testing | David Tzemach
All you need to know about regression testing | David Tzemach
Similar to Test Cases Maintaining & Documenting
Positivityofnegative
This document discusses negative testing techniques. Negative testing aims to show where software fails rather than works. It involves testing invalid inputs and edge cases to evaluate error handling and robustness. The document covers managing negative testing, techniques like boundary value analysis and error path testing, selecting impactful tests, executing them while observing failures, and addressing common criticisms of the approach. The conclusion is that negative testing finds significant failures and provides strategic information about risk, though it requires an opportunistic approach to plan and manage.
Unit 1 part 2
The document discusses 11 principles of software testing. It explains that a fault in code does not always produce a failure, as a failure only occurs when the software is unable to perform its required functions, while a fault is simply an error or defect in the code. It also discusses the roles of testers and how testing should be integrated into the software development lifecycle.
IT8076 - SOFTWARE TESTING
The document discusses 11 principles of software testing. Principle 1 defines testing as exercising software with test cases to find defects and evaluate quality. Principle 2 states that good test cases have a high probability of finding undetected defects. Principle 3 stresses the importance of meticulously inspecting test results. The remaining principles address developing test cases for valid and invalid inputs, the relationship between detected defects and potential for additional defects, independence of testing from development, repeatability/reusability of tests, planning testing, integrating testing in the software lifecycle, and the creative and challenging nature of testing.
Qa documentation pp
This document discusses software test documentation standards and processes. It describes the IEEE 829 standard for software test documentation, which includes a test planning and control process involving test plans, analysis and design involving test cases and procedures, implementation and execution involving bug reports and test procedures, and evaluation and reporting involving status reports and test logs. It provides details on various test documentation artifacts like test plans, test designs, test cases, test procedures, and reports. It explains the purpose, structure, and contents of each artifact to provide documentation at different stages of the testing process.
Exploratory Testing: Make It Part of Your Test Strategy
Developers often have the unfortunate distinction of not thoroughly testing their code. It’s not that developers do not understand how to test well; it’s just that often they have not had an opportunity to understand how the product works. Kevin Dunne maintains that implementing a team-wide exploratory testing initiative can help build the collaboration and knowledge sharing needed to elevate all team members to the level of product master. Exploratory testing can be performed by anyone, but the real challenge is making sure that the process is properly managed, documented, and optimized. Kevin describes the tools necessary to drive a deeper understanding of software quality and to implement an effective and impactful exploratory testing practice. Creating better software is not just about writing code more accurately and efficiently; it is about delivering value to the end user. Well-executed exploratory testing helps unlock this capability across the entire development team.
S440999102
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
Hai
This document outlines 11 principles of software testing:
1. Testing is the process of executing software with test cases to reveal defects and evaluate quality. Testers detect defects before software is operational.
2. A good test case has a high probability of revealing undetected defects when the objective is defect detection.
3. Testers must meticulously inspect and interpret test results to avoid overlooking failures or suspecting failures that don't exist.
Fundamental test process
The document describes the fundamental test process, which can be divided into 5 basic steps: test planning and control, test analysis and design, test implementation and execution, test evaluating exit criteria and reporting, and test closure activities. It provides details on the main tasks for each step, including developing test plans, analyzing test basis, designing and implementing tests, executing tests, evaluating whether exit criteria are met, and closing test activities.
Fundamentals of testing
This document provides an overview of fundamentals of testing. It discusses:
1. Why testing is necessary by describing how software defects can cause harm and issues if not found and fixed. Testing helps find defects and improve quality.
2. Fundamental principles of testing including that testing shows presence but not absence of defects, early testing is important, and defects tend to cluster in certain areas.
3. The fundamental test process including planning, analysis, implementation, evaluation, and closure activities for testing at all levels.
4. Psychological factors that influence testing like clear objectives, balance of self and independent testing, and courteous communication about defects found.
Fundamentals of Software Testing
This document provides an overview of fundamentals of software testing. It discusses why testing is necessary, defines key terms like errors, defects and failures. It describes the context in which software is used and how defects can impact systems. The seven principles of testing and fundamental test process involving planning, analysis, implementation and reporting are explained. Psychological aspects of testing and principles of ethical code are also covered at a high level.
L software testing
This document provides an overview of software testing concepts and best practices. It defines key terms like errors, defects, and failures. It describes different testing approaches like black box and white box testing. It also outlines different testing levels from unit to system testing. The document emphasizes that testing aims to find defects, but it's impossible to test all possibilities. It stresses the importance of test planning, test cases, defect reports, and regression testing with new versions.
Welingkar_final project_ppt_IMPORTANCE & NEED FOR TESTING
Software testing is an important step in the software development process to identify bugs and ensure quality. It is done at various stages including unit, integration, system, and acceptance testing. Automation testing helps test cases be run quickly and consistently. In conclusion, software testing is crucial to identify and remove errors, improving the performance and consistency of software products.
How to Write a Test Plan .pdf
The document provides guidance on how to write an effective test plan. It explains that a test plan is a written document that describes the methodology, parameters, tools, and timetable for testing a software solution or system. It ensures the software fulfills requirements for functionality and quality. The document outlines key components that should be included in a test plan such as test coverage, test methods, test responsibilities, resources needed, dependencies and risks. It emphasizes the importance of planning testing activities and having the necessary resources. Different types of test plans are discussed for different testing levels and types.
UNIT 1.pptx
This document provides an overview of software testing concepts. It discusses testing as an engineering activity and process. It introduces the Testing Maturity Model which describes stages of test process improvement. Basic definitions are provided for terms like error, fault, failure, test case, test oracle. Software testing principles and the tester's role are described. The origins and costs of defects are discussed. Defect classes are classified into requirements, design, code, and testing defects. The concept of a defect repository to catalog defect data is introduced. Examples of coin problem defects are given to illustrate defect classification.
Software Testing - SDLC Model
Software Testing - SDLC ModelAmity University | FMS - DU | IMT | Stratford University | KKMI International Institute | AIMA | DTU
Software Testing
Different Types of Software Testing
Verification
Validation
Unit Testing
Beta Testing
Alpha Testing
Black Box Testing
White Box testing
Error
BugIstqb lesson1
The document describes an ISTQB foundation level testing course. It discusses career paths in testing and ISTQB certifications, including the foundation, agile tester, and advanced levels. It outlines the intended audience and learning objectives of the foundation level course, which include using common testing terminology, understanding test processes and principles, designing and prioritizing tests, and executing and reporting on test results. The document then discusses the specific content and lessons that will be covered in the course.
Fundamental Test Process - APRIDILA ANGGITA SURI
The topic of this presentation is Fundamental Test Process. In the presentatio, you can find Information System Departement's site, Science and Technology Faculty's site and site of State Islamic University of Sultan Syarif Kasim Riau.
Created by:
APRIDILA ANGGITA SURI (NIM.11453205120)
Information System Departement
Science and Technology Faculty
State Islamic University of Sultan Syarif Kasim Riau
Istqb v.1.2
This document provides an overview of software testing fundamentals. It defines key terms related to testing like bugs, defects, errors, and failures. It explains why testing is important and discusses test techniques like validation, verification, static testing, and dynamic testing. The document outlines the testing process including planning, analysis, implementation, execution, evaluation, and closure. It discusses principles of testing and notes that while testing can find defects, it cannot prove that a system is completely bug-free. Exhaustive testing of all possible test cases is infeasible for most systems.
Test management
The document discusses test management for software quality assurance. It defines test management as organizing and controlling the testing process and artifacts. The goals of test management are to plan, develop, execute and assess testing activities within software development. It also discusses phases of test management like test planning, authoring, execution and reporting. It highlights challenges of test management like limited time and resources as well as priorities and classifications for testing.
MIT521 software testing (2012) v2
This document provides an overview of software testing techniques and best practices covered in a course on the topic. It discusses the purpose of software testing, including verification, error detection, and validation. It then surveys common software testing methodologies like white box testing, black box testing, and unit testing. The document also includes two case studies, one on test automation and one on testing an intranet system. Finally, it provides a template for a software test plan and discusses several papers on software testing methods and techniques.
Similar to Test Cases Maintaining & Documenting (20)
Exploratory Testing: Make It Part of Your Test Strategy
Exploratory Testing: Make It Part of Your Test Strategy
Welingkar_final project_ppt_IMPORTANCE & NEED FOR TESTING
Welingkar_final project_ppt_IMPORTANCE & NEED FOR TESTING
More from Seyed Ali Marjaie
Presentation Skills
The document provides guidance on developing effective presentation skills. It covers preparing a presentation by understanding the audience, structuring the content logically, and using visual aids. It also discusses preparing oneself through confidence, appearance, voice control, and reducing tension. When delivering the presentation, the document advises controlling nerves, speaking confidently, and closing effectively. It concludes by offering tips on judging the audience's mood and handling questions.
Immigration Management
This project involves managing an Iranian family's plan to study abroad in India. It will require obtaining admissions and accommodation for all family members, as well as arranging travel, visas, and settlement issues. A project manager will oversee the process and coordinate with stakeholders like the family members and participating institutions. Communication will occur via Skype and standard project documentation like status reports will be used to monitor progress.
Ethics
Ethics is the philosophical study of morality and right and wrong conduct. It encompasses theories of what constitutes a good life and the principles that govern behavior for individuals and groups. There are several branches of ethics, including meta-ethics which examines the meaning and justification of ethical statements, normative ethics which develops theories of right and wrong action, and applied ethics which deals with real-life ethical situations and dilemmas. The major theories in normative ethics are deontological ethics, which focuses on duties and rules, teleological ethics like utilitarianism which focuses on outcomes and consequences, and virtue ethics which focuses on character.
Dns And Snmp
The document provides an overview of the Domain Name System (DNS) and Simple Network Management Protocol (SNMP).
DNS is a hierarchical and distributed database that maps domain names to IP addresses. It allows easy-to-remember names to be used instead of hard-to-remember IP addresses. DNS follows a tree structure with top-level domains at the root and subdomains below. DNS servers resolve names to addresses through queries.
SNMP is a network management protocol that allows monitoring and controlling network devices. It uses a simple request-response mechanism to get/set variables and monitor events. SNMP defines a structure for variables and their values using an object identifier system and text files called MIBs.
Presentation On Personality
The document discusses personality from an organizational behavior perspective. It defines personality as a dynamic system greater than the sum of its parts. Personality is determined by heredity, environment, and situation. Two prominent models of personality discussed are the Myers-Briggs Type Indicator and Big Five model. Methods of measuring personality include interviews, observation, projective tests, and objective tests.
Morality And Ethic
This document discusses different perspectives on morality including conventional morality, ethical relativism, and moral absolutism. It outlines Kohlberg's stages of moral development including the pre-conventional, conventional, and post-conventional levels. It also discusses the differences between ethical relativism, which holds that morality is culturally determined, and moral absolutism, which believes in universal moral truths. The document concludes that while cultural differences exist, moral judgments can be rationally defended and contradictory judgments must have one correct view.
More from Seyed Ali Marjaie (6)
Recently uploaded
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Northern Engraving | Nameplate Manufacturing Process - 2024
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
5th LF Energy Power Grid Model Meet-up Slides
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.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Dandelion Hashtable: beyond billion requests per second on a commodity server
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).
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Artificial Intelligence and Electronic Warfare
Artificial Intelligence and Electronic WarfarePapadakis K.-Cyber-Information Warfare Analyst & Cyber Defense/Security Consultant-Hellenic MoD
AI & Electronic Warfare[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Recently uploaded (20)
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
Northern Engraving | Nameplate Manufacturing Process - 2024
Northern Engraving | Nameplate Manufacturing Process - 2024
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Test Cases Maintaining & Documenting
- 1. Revant Pande and Ali Marjaie
- 2. WHAT IS A TEST CASE? IEEE Standard 610 (1990) defines test case as follows: A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
- 9. BLACK BOX & WHITE BOX TESTING