How google tests software
•Download as PPTX, PDF•
1 like•2,866 views
Google takes a systematic approach to testing software, with roles like software engineers, engineers in test, and test engineers. Teams are organized by product, and testing occurs in stages from small to large tests across channels like development, test, beta and production. Automated tools are used for bug reporting, metrics and bots to aid various types of testing, while documentation includes test plans, cases and risk analysis.
Report
Share
Report
Share
Recommended
How google-tests-software
1. The document discusses quality processes at Google, including that testing involves many developers and one tester.
2. It describes different types of tests - unit, integration, and system - and how they are used to validate code quality and product quality at different stages.
3. Key aspects of Google's quality process include classifying tests by size, enforcing time limits, ensuring tests are independent and have no side effects, and using test results to guide continuous integration.
50 points from the book_How Google tests Software
Google takes a blended approach to software development and testing where the two practices are interwoven and indistinguishable. Testing is considered an integral part of the development process, not a separate activity. Google emphasizes automated testing and uses a tiered release process involving Canary, Dev, Test, and Beta channels to carefully test and iterate new versions before public release. The roles of Software Engineer (SWE), Software Engineer in Test (SET), and Test Engineer (TE) work together in testing with SWEs and SETs focused more on unit and integration testing and TEs focused more on user testing.
Software Testing As a Career Path
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
Chapter 2 - Testing Throughout the Development LifeCycle
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made.
The Scrum Model
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Chapter 3 - Static Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
Managing Technical Debt
This document discusses the concept of technical debt in software development. It defines technical debt as design or construction approaches that are expedient in the short term but increase costs in the long term. It provides examples of technical debt, such as skipping tests or violating coding standards to meet a deadline. The document outlines reasons for and against taking on technical debt. It also discusses tracking and paying down technical debt over time.
Chapter 2 - Fundamental Agile Testing Principle, Practices & Process
Chapter 2 of ISTQB Agile Tester extension certification. This chapter will help you prepare well on chapter 2 of Agile certification
Recommended
How google-tests-software
1. The document discusses quality processes at Google, including that testing involves many developers and one tester.
2. It describes different types of tests - unit, integration, and system - and how they are used to validate code quality and product quality at different stages.
3. Key aspects of Google's quality process include classifying tests by size, enforcing time limits, ensuring tests are independent and have no side effects, and using test results to guide continuous integration.
50 points from the book_How Google tests Software
Google takes a blended approach to software development and testing where the two practices are interwoven and indistinguishable. Testing is considered an integral part of the development process, not a separate activity. Google emphasizes automated testing and uses a tiered release process involving Canary, Dev, Test, and Beta channels to carefully test and iterate new versions before public release. The roles of Software Engineer (SWE), Software Engineer in Test (SET), and Test Engineer (TE) work together in testing with SWEs and SETs focused more on unit and integration testing and TEs focused more on user testing.
Software Testing As a Career Path
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
Chapter 2 - Testing Throughout the Development LifeCycle
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made.
The Scrum Model
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Chapter 3 - Static Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
Managing Technical Debt
This document discusses the concept of technical debt in software development. It defines technical debt as design or construction approaches that are expedient in the short term but increase costs in the long term. It provides examples of technical debt, such as skipping tests or violating coding standards to meet a deadline. The document outlines reasons for and against taking on technical debt. It also discusses tracking and paying down technical debt over time.
Chapter 2 - Fundamental Agile Testing Principle, Practices & Process
Chapter 2 of ISTQB Agile Tester extension certification. This chapter will help you prepare well on chapter 2 of Agile certification
Agile and Lean Software Development
My presentation at VTU's Faculty Development Program (FDP) organised by Computer Society of India (CSI) Bangalore on Jan 11, 2013.
BlazeMeter Presents at the High Performance Drupal Meetup
BlazeMeter is a cloud-based load testing service that is 100% compatible with Apache JMeter. It aims to simplify load testing for developers and testers by handling the infrastructure and providing an easy-to-use interface. Key features include the ability to run load tests with thousands of users in under 10 minutes, analyze response times and errors under different loads, and compare performance with caching enabled versus disabled.
Bug life cycle
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
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.
Agile Development Methodology: Best Practices and Use Cases
Taking Agile Development from Good to Great at Your Company: Learn about Agile Development Methodologies, Best Practices, and Customer Use Cases
How to report bugs
The document provides guidance on writing effective bug reports to help ensure bugs get fixed. Key points include:
1) Bug reports should be reproducible, specific, and assign a unique identifier.
2) Clearly specify steps to reproduce the bug, expected results, and actual results.
3) Use a standardized template to maintain consistency and provide necessary details about the bug.
Agile Methodology PPT
This Presentation shows That what is Agile methodology, its principles and key points and how it is different from other software development life cycle.
FDD Overview
Presentation about FDD (Feature-Driven Development) for the "Alles Ausser Scrum" conference in Cologne, Germany, on 5th April 2019
Extreme programming (xp)
This document provides an overview of Extreme Programming (XP), an agile software development methodology. It discusses XP's history and features, which include short 2-week development cycles, pair programming, test-driven development, and frequent refactoring. The core principles of XP are also examined, such as incremental planning, small releases, simple design, and sustainable pace. Various phases of the XP process are outlined, from exploration to productionizing. Requirements are captured as scenarios and prioritized by the customer. Automated testing is a key practice in XP. Both advantages like collective code ownership and disadvantages like its unsuitability for large projects are noted.
Domain-Specific Software Engineering
The document discusses domain-specific software engineering and how it differs from traditional technology-centric approaches. It argues that domain-specific knowledge is better encoded through domain-specific modeling, middleware, and languages rather than through operations, run-time state, or generic programming languages. This allows capturing domain concepts, rules, and semantics to generate customized implementations and improve software robustness, re-use, and verification.
Agile Test Driven Development
A quick paced introduction to "Test Driven Development" (TDD) in an agile environment. The TDD philosophy states that you should develop your tests and then write code to make your tests pass and satisfy user requirements.
Chapter 5 - Test Management
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
Go Jira
The GoJira presentation is an introduction to the the concepts in Atlassian Jira. It suggest some best practices for both beginning and experienced Jira users. The author has been using Jira since 2005 and written several plugins for the system.
Chapter 5 - Improving the Testing Process
This is chapter 5 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 6 - Tool Support for Testing
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation, Risk of Test Automation, Selecting a tool for Organization, Pilot Project, Success factor for using a tool
Extreme Programming ppt
This document provides an overview of Extreme Programming (XP), a software development methodology. It discusses key XP practices like user stories, acceptance tests, release planning, refactoring, and pair programming. XP aims to improve communication, keep designs simple, provide frequent feedback through testing, and encourage courage in decision making. It emphasizes delivering working software frequently in short iterations to ensure customer needs are met.
Scrum Framework
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
Jira as a Project Management Tool
This presentation gives a brief description about how you can adopt Jira as a Project Management Tool
New trends in testing automation
This document discusses keyword-driven testing (KDT), a method for automating tests without programming. KDT allows manual testers and subject matter experts to design and execute automated test scripts. The document outlines the benefits of KDT, such as increased test coverage and faster return on investment. It also describes some challenges, such as maintenance issues. Overall, KDT is presented as the next generation of test automation that can empower users and drive organizational adoption of automated testing tools.
Release Management: Successful Software Releases Start with a Plan
This document discusses the importance of release planning for successful software releases. It notes that even with agile development, a release plan is needed to coordinate releasing software to users. The document outlines different types of release cycles including time-based, feature-based, and market demand-based. It also discusses factors to consider when deciding on a release cycle. Additionally, it provides details on what should be included in a release plan such as goals, features, milestones, responsibilities, dependencies, and risks. The document stresses the importance of communication and ensuring product readiness to have successful software releases.
How Google Tests Software (구글의 소프트웨어 테스팅)
"How Google Tests Software" 서적 내용을 바탕으로 구글의 소프트웨어 테스팅이 어떠한 방식으로 수행되는지, 각 엔지니어의 역할은 무엇인지 요약해놓은 자료입니다.
Software testability slide share
This document discusses software testability. It defines testability and explains why it is important. High testability results in more effective testing and lower costs. Testability is improved by controllability, observability, availability, simplicity, stability, information, and operability. A tool called Testability-Explorer can analyze testability and produce a testability report. The document concludes that designing for testability helps produce high quality software.
More Related Content
What's hot
Agile and Lean Software Development
My presentation at VTU's Faculty Development Program (FDP) organised by Computer Society of India (CSI) Bangalore on Jan 11, 2013.
BlazeMeter Presents at the High Performance Drupal Meetup
BlazeMeter is a cloud-based load testing service that is 100% compatible with Apache JMeter. It aims to simplify load testing for developers and testers by handling the infrastructure and providing an easy-to-use interface. Key features include the ability to run load tests with thousands of users in under 10 minutes, analyze response times and errors under different loads, and compare performance with caching enabled versus disabled.
Bug life cycle
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
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.
Agile Development Methodology: Best Practices and Use Cases
Taking Agile Development from Good to Great at Your Company: Learn about Agile Development Methodologies, Best Practices, and Customer Use Cases
How to report bugs
The document provides guidance on writing effective bug reports to help ensure bugs get fixed. Key points include:
1) Bug reports should be reproducible, specific, and assign a unique identifier.
2) Clearly specify steps to reproduce the bug, expected results, and actual results.
3) Use a standardized template to maintain consistency and provide necessary details about the bug.
Agile Methodology PPT
This Presentation shows That what is Agile methodology, its principles and key points and how it is different from other software development life cycle.
FDD Overview
Presentation about FDD (Feature-Driven Development) for the "Alles Ausser Scrum" conference in Cologne, Germany, on 5th April 2019
Extreme programming (xp)
This document provides an overview of Extreme Programming (XP), an agile software development methodology. It discusses XP's history and features, which include short 2-week development cycles, pair programming, test-driven development, and frequent refactoring. The core principles of XP are also examined, such as incremental planning, small releases, simple design, and sustainable pace. Various phases of the XP process are outlined, from exploration to productionizing. Requirements are captured as scenarios and prioritized by the customer. Automated testing is a key practice in XP. Both advantages like collective code ownership and disadvantages like its unsuitability for large projects are noted.
Domain-Specific Software Engineering
The document discusses domain-specific software engineering and how it differs from traditional technology-centric approaches. It argues that domain-specific knowledge is better encoded through domain-specific modeling, middleware, and languages rather than through operations, run-time state, or generic programming languages. This allows capturing domain concepts, rules, and semantics to generate customized implementations and improve software robustness, re-use, and verification.
Agile Test Driven Development
A quick paced introduction to "Test Driven Development" (TDD) in an agile environment. The TDD philosophy states that you should develop your tests and then write code to make your tests pass and satisfy user requirements.
Chapter 5 - Test Management
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
Go Jira
The GoJira presentation is an introduction to the the concepts in Atlassian Jira. It suggest some best practices for both beginning and experienced Jira users. The author has been using Jira since 2005 and written several plugins for the system.
Chapter 5 - Improving the Testing Process
This is chapter 5 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 6 - Tool Support for Testing
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation, Risk of Test Automation, Selecting a tool for Organization, Pilot Project, Success factor for using a tool
Extreme Programming ppt
This document provides an overview of Extreme Programming (XP), a software development methodology. It discusses key XP practices like user stories, acceptance tests, release planning, refactoring, and pair programming. XP aims to improve communication, keep designs simple, provide frequent feedback through testing, and encourage courage in decision making. It emphasizes delivering working software frequently in short iterations to ensure customer needs are met.
Scrum Framework
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
Jira as a Project Management Tool
This presentation gives a brief description about how you can adopt Jira as a Project Management Tool
New trends in testing automation
This document discusses keyword-driven testing (KDT), a method for automating tests without programming. KDT allows manual testers and subject matter experts to design and execute automated test scripts. The document outlines the benefits of KDT, such as increased test coverage and faster return on investment. It also describes some challenges, such as maintenance issues. Overall, KDT is presented as the next generation of test automation that can empower users and drive organizational adoption of automated testing tools.
Release Management: Successful Software Releases Start with a Plan
This document discusses the importance of release planning for successful software releases. It notes that even with agile development, a release plan is needed to coordinate releasing software to users. The document outlines different types of release cycles including time-based, feature-based, and market demand-based. It also discusses factors to consider when deciding on a release cycle. Additionally, it provides details on what should be included in a release plan such as goals, features, milestones, responsibilities, dependencies, and risks. The document stresses the importance of communication and ensuring product readiness to have successful software releases.
What's hot (20)
BlazeMeter Presents at the High Performance Drupal Meetup
BlazeMeter Presents at the High Performance Drupal Meetup
Agile Development Methodology: Best Practices and Use Cases
Agile Development Methodology: Best Practices and Use Cases
Release Management: Successful Software Releases Start with a Plan
Release Management: Successful Software Releases Start with a Plan
Viewers also liked
How Google Tests Software (구글의 소프트웨어 테스팅)
"How Google Tests Software" 서적 내용을 바탕으로 구글의 소프트웨어 테스팅이 어떠한 방식으로 수행되는지, 각 엔지니어의 역할은 무엇인지 요약해놓은 자료입니다.
Software testability slide share
This document discusses software testability. It defines testability and explains why it is important. High testability results in more effective testing and lower costs. Testability is improved by controllability, observability, availability, simplicity, stability, information, and operability. A tool called Testability-Explorer can analyze testability and produce a testability report. The document concludes that designing for testability helps produce high quality software.
Software testing 2012 - A Year in Review
The document summarizes software testing trends in 2012. Key points include: Google introduced "Testing 2.0" which focuses on risk assessment and reducing probabilities of bugs; good test automation requires caring about results and addressing failed tests; context-driven testing emphasizes a risk-based approach and looking at multiple contexts rather than one school of thought; mindless automation and scripted manual regression testing are not effective at finding bugs; and customer involvement is important for testing in agile projects.
Software testing Report
The document provides guidance on software testing reports. A test report should document the results of testing defined in the test plan and serve three objectives: define the testing scope, present results, and provide conclusions and recommendations. An example test summary report for a bus ticket booking application is provided covering testing scope, types of testing, metrics, environment, lessons learned, best practices, and exit criteria. The report aims to communicate testing results to stakeholders.
Google Analytics
The document discusses various ways to track user interactions on websites beyond traditional pageviews using Google Analytics and other common technologies. It provides examples of specific interactions that can be tracked, like clicks, mouse movements, and steps in a checkout process. It also addresses questions about implementing analytics code, testing, overhead, and best practices.
Google Case Study
The document discusses Google's business strategy and potential areas for expansion. It summarizes that Google started as a search engine and used innovative paid listing and algorithmic models to grow rapidly. While competitors pursued diversification, Google achieved differentiation through superior search quality and a focus on innovation. The summary recommends that Google continue focusing on its core search competency in line with its 70-20-10 strategy, given its competitive advantages in this area. Direct competition with established players in other domains like portals, ecommerce or operating systems would be challenging.
Viewers also liked (7)
Recently uploaded
UiPath Test Automation using UiPath Test Suite series, part 5
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
GridMate - End to end testing is a critical piece to ensure quality and avoid...
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications.
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
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
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar
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.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Recently uploaded (20)
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
GridMate - End to end testing is a critical piece to ensure quality and avoid...
GridMate - End to end testing is a critical piece to ensure quality and avoid...
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
How google tests software
- 1. How Google Tests Software BY JAMES WHITTAKER
- 2. Agenda Quality process Roles Organizational Structure Continuous integration Types of Tests Tools Documentation
- 3. Google
- 4. Quality process Quality ≠ Test
- 8. Types of Tests Large tests Medium tests Small tests
- 11. The End