Databasedemo3
•Download as PPTX, PDF•
1 like•846 views
This document outlines the manufacturing testing process for an integrated circuit design company. It includes wafer acceptance testing, final testing of chips through probing, and packing and data testing. The document also mentions roles like product engineer, test engineer, quality engineer, and management leader that are involved in research and development, testing, quality control, and providing 24/7 support and services to save time and costs.
Report
Share
Report
Share
Recommended
Key Measurements For Testers
This document discusses key measurements for testers, including precision vs accuracy. It provides examples to illustrate the difference between precision and accuracy. The document also discusses goals for testing, including using the SMART framework. It introduces the GQM methodology for defining test goals and questions. Additional sections cover test planning and resources, defect tracking, defect prediction, and release criteria.
Test strategy consecration for agile and devops
This document discusses strategies for test consecration in Agile and DevOps environments. It notes that testing is an ongoing task that is part of the development team's DNA. The strategies address the Agile test process maturity, what to test in sprints and parallel to sprints, testing optimization process, testing tool selection, and testing in DoD, CI/CD/CT pipelines and integration. The author provides their email for anyone with additional questions.
Key Measurements For Testers
This document discusses key measurements for testers, including precision vs accuracy, goals for testing (SMART goals), the GQM methodology for defining test goals and questions, and various metrics for evaluating projects, products, and releases such as defect rates and trends. It provides examples of defining test plans and resources needed, tracking reported vs resolved defects, and criteria for determining when a release is ready.
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Quality engineering approaches (published)
Quality Engineering Approaches by Yotam Sharan
A lecture given by Yotam on October 8, 2013 at eBay Israel Development Center, as part of eBay's QA Conference.
Why Automated Testing Matters To DevOps
“Automated testing is a pain in my ear! Why can’t QA get it right? Why do the tests keep breaking? And for Pete’s sake, stop blaming the infrastructure!”
…Ok, maybe you chose a different word than “ear”.
How often do you have thoughts like this? Daily?
Let’s talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!
DevOps Summit 2015 Presentation: Continuous Testing At the Speed of DevOps
Continuous delivery is frightening to enterprise IT managers who see each new private, public or hybrid cloud infrastructure software change potentially causing service outages or security concerns.
This presentation by Marc Hornbeek, first shared at the DevOps Summit 2015 in London, explains Spirent’s comprehensive Clear DevOps Solution to support:
- Rapid paced continuous testing without compromising coverage or service quality
- Orchestration of service deployments over physical and virtual infrastructures
- Best practices for integrating continuous testing into CI infrastructures
- How to use continuous testing analytics for deployment decisions
Agile Testing Agile Ottawa April 2015
Agile testing focuses on delivering valuable working software through collaboration, feedback, and automation. It involves the whole team taking responsibility for quality. Agile testers provide continuous feedback, prioritize value, and think critically to challenge assumptions and find problems. They collaborate with developers to shift testing left in the SDLC through approaches like specification by example and behavior driven development which define examples of desired behavior to build shared understanding.
Recommended
Key Measurements For Testers
This document discusses key measurements for testers, including precision vs accuracy. It provides examples to illustrate the difference between precision and accuracy. The document also discusses goals for testing, including using the SMART framework. It introduces the GQM methodology for defining test goals and questions. Additional sections cover test planning and resources, defect tracking, defect prediction, and release criteria.
Test strategy consecration for agile and devops
This document discusses strategies for test consecration in Agile and DevOps environments. It notes that testing is an ongoing task that is part of the development team's DNA. The strategies address the Agile test process maturity, what to test in sprints and parallel to sprints, testing optimization process, testing tool selection, and testing in DoD, CI/CD/CT pipelines and integration. The author provides their email for anyone with additional questions.
Key Measurements For Testers
This document discusses key measurements for testers, including precision vs accuracy, goals for testing (SMART goals), the GQM methodology for defining test goals and questions, and various metrics for evaluating projects, products, and releases such as defect rates and trends. It provides examples of defining test plans and resources needed, tracking reported vs resolved defects, and criteria for determining when a release is ready.
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Quality engineering approaches (published)
Quality Engineering Approaches by Yotam Sharan
A lecture given by Yotam on October 8, 2013 at eBay Israel Development Center, as part of eBay's QA Conference.
Why Automated Testing Matters To DevOps
“Automated testing is a pain in my ear! Why can’t QA get it right? Why do the tests keep breaking? And for Pete’s sake, stop blaming the infrastructure!”
…Ok, maybe you chose a different word than “ear”.
How often do you have thoughts like this? Daily?
Let’s talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!
DevOps Summit 2015 Presentation: Continuous Testing At the Speed of DevOps
Continuous delivery is frightening to enterprise IT managers who see each new private, public or hybrid cloud infrastructure software change potentially causing service outages or security concerns.
This presentation by Marc Hornbeek, first shared at the DevOps Summit 2015 in London, explains Spirent’s comprehensive Clear DevOps Solution to support:
- Rapid paced continuous testing without compromising coverage or service quality
- Orchestration of service deployments over physical and virtual infrastructures
- Best practices for integrating continuous testing into CI infrastructures
- How to use continuous testing analytics for deployment decisions
Agile Testing Agile Ottawa April 2015
Agile testing focuses on delivering valuable working software through collaboration, feedback, and automation. It involves the whole team taking responsibility for quality. Agile testers provide continuous feedback, prioritize value, and think critically to challenge assumptions and find problems. They collaborate with developers to shift testing left in the SDLC through approaches like specification by example and behavior driven development which define examples of desired behavior to build shared understanding.
Dietmar Strasser - Traditional QA meets Agile Development
EuroSTAR Software Testing Conference 2008 presentation on Traditional QA meets Agile Development by Dietmar Strasser. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Quality Loopback
The ability to deliver software to production speedily and reliably is critical to supporting a disruptive business landscape and covering implementation gaps. A key factor inhibiting this is testing. DevOps practices encourage shifting left, i.e., testing more during development using unit and component test rather than with QA using end-to-end tests. However, unit and component testing lack functional coverage that may exist in QA end-to-end tests. Shifting left with a domain focus may lead to component and unit tests that don't just guarantee that the software is built right but also that the right software is build.
Continuous testing the new must have skill of tomorrow's tech leaders
Continuous testing the new must have skill of tomorrow's tech leadersNadav Yeheskel - Looking for a Test/QA engineer
The document discusses continuous testing and the role of a tech lead in implementing it. It explains that continuous testing involves testing software continuously throughout development. To be a continuous testing expert, a tech lead should master different testing techniques, identify what code needs testing, set a testing culture, collect and analyze testing metrics, and use insights to improve processes. The document demonstrates continuous testing in action through an automated CI/CD workflow that runs unit, integration and other tests at different stages.Keynote AST 2016
The document discusses various aspects of automating software testing. It suggests automating the detection of flaky tests, determining the severity of test failures, converting tests to more isolated unit tests, and using usage data to determine what to test next. It emphasizes that while automation can improve testing efficiency, human oversight is still needed, and code reviews serve as the link between automated and manual processes.
Being a Professional Software Developer
Talk from Agile Saturday 3 event in Estonia.
It is about being professional in general as well as following agile best practices, such as build automation and continuous integration.
Shift Left Testing: Going Beyond Agile
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...
This document discusses the transformation of a QA organization to a test engineering organization. It provides historical context on the evolution of testing techniques from the 1970s to present. It then details the specific transformation journey the organization took, including providing awareness training, mentorship, skills assessments, hiring test engineers, and establishing partnerships with offshore test engineering firms. The results were removing barriers between manual and automation testing, enabling more associates to use automation, and shifting testing upstream. Future trends of testing as a developer responsibility and increasing automation are also discussed.
The Thinking Tester, Evolved
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
Definition of Done
The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.
tem7
Test Driven Development (TDD) is a software development technique where unit tests are written before functional code to verify functionality. The TDD process follows a "Red, Green, Refactor" cycle where tests fail initially ("Red"), code is written to pass tests ("Green"), and code is refactored to improve design. While TDD may improve code quality and catch errors earlier, studies have shown mixed results on productivity and quality improvements. Adopting TDD fully can be challenging in practice due to issues like incomplete test coverage and resistance to change.
Continuous Delivery & Testing Madrid AfterTest
This document discusses continuous delivery and the testing challenges it presents. It describes a large financial institution's goal of delivering updates to their digital payment platform weekly. Initially they had a 9 month release cycle with many sequential test phases. The author proposed reducing features per release and incorporating more testing into development. This faced resistance from test managers concerned about quality and independent testing. Through education and demonstrations, the approach was modified to have functional testing after development and the culture shifted to prioritize automated testing and quality as everyone's responsibility.
Role of high-level project professionals perceptions on quality processes in ...
1) The document explores how high-level professionals' perceptions of quality processes can direct investigations into the causes of premature pavement failures.
2) Interviews and questionnaires given to contractor, consultant, and owner representatives on two projects found differing attitudes about construction supervision, quality testing, and contract documentation.
3) Their perceptions provided indicators about understanding of specifications, communication of information, and awareness of quality processes, which can help identify the root causes of premature pavement distress.
Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...
The document discusses the evolving role of software testers and the benefits of testers becoming software development engineers in test (SDETs). It argues that testers should expand their skills from just testing to also include activities like programming, test automation, and code reviews. This will allow testers to find defects earlier and help reduce test cycle times. It outlines a path for testers to transition to SDETs by improving their technical skills and provides examples of how SDETs have contributed value in various organizations.
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Quality Jam: BDD, TDD and ATDD for the Enterprise
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
Moving QA from Reactive to Proactive with qTest
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
Devopsdays.pl 2015 krzysztof_debski (2)
This document summarizes the key lessons learned from a one year experience with a DevOps team. It discusses mixing developers and operations teams, how building high performance applications requires DevOps, and how taking multiple viewpoints is necessary to fix all problems. The document also provides background on the speaker, their company Allegro Group, and links to additional resources.
Agile Testing
This document introduces concepts of agile testing and compares it to traditional testing practices. It discusses the fundamental shift in thought process required for agile testing and provides some pointers on tools and techniques used. The traditional software development process involves separate sequential phases of analyze, design, code, and test/bug fix, while agile embraces uncertainty and a more iterative approach.
The Role of Testing in DevOps
The document discusses the role of testing in DevOps. It emphasizes that testing should happen at all stages of development from unit tests to acceptance tests to load and performance tests. Modern testing approaches advocate for automating tests and avoiding manual repetition through techniques like fractal testing. The goal is to shift testing left and catch bugs earlier to improve code quality and allow developers to focus on writing new code instead of fixing old bugs.
Trends in Agile Testing by Lisa Crispin
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
Main news related to the CCS TSI 2023 (2023/1695)
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 .
More Related Content
What's hot
Dietmar Strasser - Traditional QA meets Agile Development
EuroSTAR Software Testing Conference 2008 presentation on Traditional QA meets Agile Development by Dietmar Strasser. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Quality Loopback
The ability to deliver software to production speedily and reliably is critical to supporting a disruptive business landscape and covering implementation gaps. A key factor inhibiting this is testing. DevOps practices encourage shifting left, i.e., testing more during development using unit and component test rather than with QA using end-to-end tests. However, unit and component testing lack functional coverage that may exist in QA end-to-end tests. Shifting left with a domain focus may lead to component and unit tests that don't just guarantee that the software is built right but also that the right software is build.
Continuous testing the new must have skill of tomorrow's tech leaders
Continuous testing the new must have skill of tomorrow's tech leadersNadav Yeheskel - Looking for a Test/QA engineer
The document discusses continuous testing and the role of a tech lead in implementing it. It explains that continuous testing involves testing software continuously throughout development. To be a continuous testing expert, a tech lead should master different testing techniques, identify what code needs testing, set a testing culture, collect and analyze testing metrics, and use insights to improve processes. The document demonstrates continuous testing in action through an automated CI/CD workflow that runs unit, integration and other tests at different stages.Keynote AST 2016
The document discusses various aspects of automating software testing. It suggests automating the detection of flaky tests, determining the severity of test failures, converting tests to more isolated unit tests, and using usage data to determine what to test next. It emphasizes that while automation can improve testing efficiency, human oversight is still needed, and code reviews serve as the link between automated and manual processes.
Being a Professional Software Developer
Talk from Agile Saturday 3 event in Estonia.
It is about being professional in general as well as following agile best practices, such as build automation and continuous integration.
Shift Left Testing: Going Beyond Agile
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...
This document discusses the transformation of a QA organization to a test engineering organization. It provides historical context on the evolution of testing techniques from the 1970s to present. It then details the specific transformation journey the organization took, including providing awareness training, mentorship, skills assessments, hiring test engineers, and establishing partnerships with offshore test engineering firms. The results were removing barriers between manual and automation testing, enabling more associates to use automation, and shifting testing upstream. Future trends of testing as a developer responsibility and increasing automation are also discussed.
The Thinking Tester, Evolved
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
Definition of Done
The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.
tem7
Test Driven Development (TDD) is a software development technique where unit tests are written before functional code to verify functionality. The TDD process follows a "Red, Green, Refactor" cycle where tests fail initially ("Red"), code is written to pass tests ("Green"), and code is refactored to improve design. While TDD may improve code quality and catch errors earlier, studies have shown mixed results on productivity and quality improvements. Adopting TDD fully can be challenging in practice due to issues like incomplete test coverage and resistance to change.
Continuous Delivery & Testing Madrid AfterTest
This document discusses continuous delivery and the testing challenges it presents. It describes a large financial institution's goal of delivering updates to their digital payment platform weekly. Initially they had a 9 month release cycle with many sequential test phases. The author proposed reducing features per release and incorporating more testing into development. This faced resistance from test managers concerned about quality and independent testing. Through education and demonstrations, the approach was modified to have functional testing after development and the culture shifted to prioritize automated testing and quality as everyone's responsibility.
Role of high-level project professionals perceptions on quality processes in ...
1) The document explores how high-level professionals' perceptions of quality processes can direct investigations into the causes of premature pavement failures.
2) Interviews and questionnaires given to contractor, consultant, and owner representatives on two projects found differing attitudes about construction supervision, quality testing, and contract documentation.
3) Their perceptions provided indicators about understanding of specifications, communication of information, and awareness of quality processes, which can help identify the root causes of premature pavement distress.
Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...
The document discusses the evolving role of software testers and the benefits of testers becoming software development engineers in test (SDETs). It argues that testers should expand their skills from just testing to also include activities like programming, test automation, and code reviews. This will allow testers to find defects earlier and help reduce test cycle times. It outlines a path for testers to transition to SDETs by improving their technical skills and provides examples of how SDETs have contributed value in various organizations.
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Quality Jam: BDD, TDD and ATDD for the Enterprise
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
Moving QA from Reactive to Proactive with qTest
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
Devopsdays.pl 2015 krzysztof_debski (2)
This document summarizes the key lessons learned from a one year experience with a DevOps team. It discusses mixing developers and operations teams, how building high performance applications requires DevOps, and how taking multiple viewpoints is necessary to fix all problems. The document also provides background on the speaker, their company Allegro Group, and links to additional resources.
Agile Testing
This document introduces concepts of agile testing and compares it to traditional testing practices. It discusses the fundamental shift in thought process required for agile testing and provides some pointers on tools and techniques used. The traditional software development process involves separate sequential phases of analyze, design, code, and test/bug fix, while agile embraces uncertainty and a more iterative approach.
The Role of Testing in DevOps
The document discusses the role of testing in DevOps. It emphasizes that testing should happen at all stages of development from unit tests to acceptance tests to load and performance tests. Modern testing approaches advocate for automating tests and avoiding manual repetition through techniques like fractal testing. The goal is to shift testing left and catch bugs earlier to improve code quality and allow developers to focus on writing new code instead of fixing old bugs.
Trends in Agile Testing by Lisa Crispin
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
What's hot (20)
Dietmar Strasser - Traditional QA meets Agile Development
Dietmar Strasser - Traditional QA meets Agile Development
Continuous testing the new must have skill of tomorrow's tech leaders
Continuous testing the new must have skill of tomorrow's tech leaders
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...
Role of high-level project professionals perceptions on quality processes in ...
Role of high-level project professionals perceptions on quality processes in ...
Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...
Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
Recently uploaded
Main news related to the CCS TSI 2023 (2023/1695)
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 .
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
OpenID AuthZEN Interop Read Out - Authorization
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
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.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Recently uploaded (20)
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Databasedemo3
- 1. Manufacture Testing and Analysis with Client EDA Tools For IC Design Company Alex Jou jou1208@gmail.com
- 5. Product Engineer Test Engineer Quality Engineer Management Leader R & D instant Accuracy Overall Automation Security improvement
- 6. Anytime Anyplace Control Headquarter 7/24 Service Time & cost Saving Foundry Testing RD QC