Darshan Desai - Virtual Test Labs,The Next Frontier - EuroSTAR 2010
•
0 likes•552 views
EuroSTAR Software Testing Conference 2010 presentation on Virtual Test Labs,The Next Frontier by Darshan Desai. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Report
Share
Report
Share
Download to read offline
Recommended
Otto Vinter - Analysing Your Defect Data for Improvement Potential
EuroSTAR Software Testing Conference 2008 presentation on Analysing Your Defect Data for Improvement Potential by Otto Vinter. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Darius Silingas - From Model Driven Testing to Test Driven Modelling
EuroSTAR Software Testing Conference 2010 presentation on From Model Driven Testing to Test Driven Modelling by Darius Silingas. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Derk jan de Grood - ET, Best of Both Worlds
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software Testing
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Inrotduction of Testing
This document discusses software testing and outlines the development planning process. It describes project requirement documents, wireframes, and mockups. Wireframes provide the basic structure and layout, while mockups add color and graphics. The document then defines software testing as evaluating a system to find errors and ensure it meets requirements. Different types of testing are outlined, including full regression testing, ad-hoc testing, and retesting. Causes of software defects and how testing improves quality are also summarized.
Test pyramid
The document discusses different types of software tests including unit tests, integration tests, service tests, and UI end-to-end tests. Unit tests check individual components, integration tests verify communication between components, service tests validate API requests and responses, and UI end-to-end tests simulate user interactions to check the full application. The document also provides an example of a student result service test response.
Best Practices In Exploratory Testing
Exploratory testing involves simultaneous test design, execution, and learning without pre-set test cases. Testers are free to explore the product like real users to find bugs missed in scripted testing. It is useful early in development when requirements are vague and the system is unstable. Challenges include needing experienced testers and careful documentation. Crowd testing can help overcome challenges by providing skilled testers across devices and locations. Exploratory testing finds critical bugs quickly and improves scripted tests and product understanding by encouraging creativity and new perspectives.
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...Ho Chi Minh City Software Testing Club
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.Recommended
Otto Vinter - Analysing Your Defect Data for Improvement Potential
EuroSTAR Software Testing Conference 2008 presentation on Analysing Your Defect Data for Improvement Potential by Otto Vinter. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Darius Silingas - From Model Driven Testing to Test Driven Modelling
EuroSTAR Software Testing Conference 2010 presentation on From Model Driven Testing to Test Driven Modelling by Darius Silingas. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Derk jan de Grood - ET, Best of Both Worlds
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software Testing
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Inrotduction of Testing
This document discusses software testing and outlines the development planning process. It describes project requirement documents, wireframes, and mockups. Wireframes provide the basic structure and layout, while mockups add color and graphics. The document then defines software testing as evaluating a system to find errors and ensure it meets requirements. Different types of testing are outlined, including full regression testing, ad-hoc testing, and retesting. Causes of software defects and how testing improves quality are also summarized.
Test pyramid
The document discusses different types of software tests including unit tests, integration tests, service tests, and UI end-to-end tests. Unit tests check individual components, integration tests verify communication between components, service tests validate API requests and responses, and UI end-to-end tests simulate user interactions to check the full application. The document also provides an example of a student result service test response.
Best Practices In Exploratory Testing
Exploratory testing involves simultaneous test design, execution, and learning without pre-set test cases. Testers are free to explore the product like real users to find bugs missed in scripted testing. It is useful early in development when requirements are vague and the system is unstable. Challenges include needing experienced testers and careful documentation. Crowd testing can help overcome challenges by providing skilled testers across devices and locations. Exploratory testing finds critical bugs quickly and improves scripted tests and product understanding by encouraging creativity and new perspectives.
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...Ho Chi Minh City Software Testing Club
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.Hey You Got Your TDD in my SQL DB by Jeff McKenzie
TDD involves writing tests before writing code to satisfy requirements. The document discusses TDD, providing:
1. An overview of the TDD process and definitions of its key steps - make a test, make it fail, make it pass.
2. An example walking through writing a test for an "easy button" and implementing the code to pass the test.
3. Reasons for using TDD, including improved code quality, design, discipline, and documentation from maintaining an automated test suite.
Myths and reality about software testing
Most of the people might say that software test engineers do not write code. Testers normally need completely different skill set which could be a mix of Java, C, Ruby, and Python.
That is not all you require to be a successful tester. A tester requires having a good knowledge of the software manuals and automation tools.
Depending on the complexity of a project, a software testing engineer may write more complicated code than the developer.
Agile Testing - Not Just Tester’s Story _ Dang Thanh Long
This topic will focus on how testing should be understood/supported/changed for all levels including customer, executives and development team (Dev, QA…) during adopting Agile methodologies, especially testing mindset. Besides that, this topic could also cover some lessons learnt from some Agile testing practices.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Achieve Intelligent Test Execution: Strategies for Streamlining Regression Te...
If you ask a business leader which features in a given software release are most critical (and which potential failures keep them up at night), chances are they'll be related to the UI. But with many testing teams spending up to 80% of their time on regression testing, how can you make time for the resource-intensive tests that verify these high business value features? In this webinar, Adam Satterfield will share strategies for optimizing the plan and build phases of a project to eliminate redundancy and free up time for the tests that matter most to the business, including:
The questions you should ask business leaders before the build begins
Why it's critical for testers to give feedback during build output and unit test reviews
How to segment UI tests to focus on validating business-critical features first
Why adopting this approach can turn good test engineers into great ones -- and improve manual testers' technical aptitude
Istqb intro with question answer for exam preparation
The document provides an overview of software testing concepts including definitions of software testing, who can perform testing, common terminology, the software development life cycle (SDLC), testing methods and levels, and more. It defines software testing as the process of comparing expected and actual results to identify defects. It outlines the typical stages of the SDLC as initial, analysis, design, coding, testing, and delivery/maintenance phases. It also describes black box, white box, and grey box testing methods and the five levels of testing: unit, module, integration, system, and acceptance.
38475471 qa-and-software-testing-interview-questions-and-answers
The document discusses software testing concepts including:
- Quality assurance ensures processes are established to produce products that meet specifications.
- Testing determines if a product meets requirements and identifies failures to meet requirements.
- A test plan is written by the lead tester and includes the testing strategy, resources, and plans. It outlines test cases and procedures to validate software meets specifications.
- Testing begins in the define system phase to ensure requirements are testable, and continues through subsequent phases including product testing, acceptance testing, and deployment. Documentation and repeatable processes are critical to quality assurance.
Wim Demey - Regression Testing in a Migration Project
EuroSTAR Software Testing Conference 2009 presentation on Regression Testing in a Migration Project by Wim Demey. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Software testing interview Q&A – Part 2
This is collection of question & answer in software testing interview job. Part 2 with 10 questions and answers.
This is designed by Khoa Bui, which owner of http://www.testing.com.vn site
Automation testing in Agile project
The document summarizes best practices for test automation, including:
- Unit tests should be automated as the first step and follow naming conventions.
- Integration and performance tests require grouping, isolation, and handling test data issues.
- UI tests can be automated with Selenium and integrated into the build pipeline.
- Automated test data, code, and plan generation may be useful once a project's structure stabilizes.
- Automation aims to provide transparency, improve skills, and reduce manual work over time through a smarter approach.
Test Design with Action-based Testing Methodology - Ngo Hoang Minh
Test Design with Action-based Testing Methodology - Ngo Hoang MinhHo Chi Minh City Software Testing Club
Nowadays in IT market, most of enterprises are trying to adopt agile and DevOps methodology to meet the time-to-market expectations and continue satisfying their customers. As the result, continue deploying new applications are become challenges for any software development teams.
During the development cycles, several questions has been identified and one of the most interesting questions is How to fit automated tests into agile projects because within agile sprints, there is simply not enough time to automate the set of tests?
Action Based Testing (ABT) methodology is becoming a solution to help you achieve your expectations on automated test coverage within the Agile iterations/sprints.
ABT uses a modular keyword-driven approach which tests are organized in test modules and are built up of sequences of actions. Well-defined test modules can provide a healthy framework for teams to work with, in particular if modules have a clear and unambiguous scope, the scope is well-differentiated from other test modules, and all test cases …within the test module reflect the scope.
A key differentiation is between business tests and interaction tests. Business tests have a business-oriented scope and should not contain UI details. Interaction tests focus on the interaction between the user (or another system) and the application.
This topic is about how to apply ABT methodologies into SDLC with some discussions on the three Holy Grail of test design approaches from Hans Buwalda. Rapid software testing
This document discusses an introduction to a class on rapid software testing. It states that the class aims to make students stronger, smarter and more confident testers by challenging them to think for themselves rather than simply listening to what the instructors say. The class can be beneficial for testers of all experience levels who want to improve at their work. Heuristics are discussed as techniques that can help substitute for complete analysis and involve guidewords, triggers, reframing ideas, and procedures to help solve problems.
Use Automation to Assist—Not Replace—Manual Testing
Automation is a powerful tool to help testing but too often it is used to replicate existing manual tests. This leads organizations to spend large amounts of time and money constantly updating flaky automated tests and test teams to suffer frustration from having to focus on activities that are not truly testing. This cost and frustration can be avoided by using automation as a tool to assist testing—not to replace tests. Jeffrey Martin shares some real-world examples of using automation to supplement testing by leveraging its true value—the replication and repetition of tasks instead of tests. Examples are drawn from several testing teams, as well as his own. Jeffrey explores what kinds of tasks are the best fit for automation, identifies which tasks are better left to testers, and provides examples of melding task automation and manual tests together. Jeffrey discusses how organizations have introduced these concepts to maximize adoption and team buy-in. Leave with a different view of automation and ideas on how to best use this powerful tool to supplement actual tests seamlessly in your own team.
The Leaders Guide to Getting Started with Automated Testing
Conventional testing is yesterday’s news, is required but needs the same overhaul that has happened in development. It needs to be a slicker operation that really identifies the risk associated with release and protects the business from serious system failure. The only way to achieve this is to remove the humans, they are prone to error, take a long time, cost a lot of money and don’t always do what they are told.
Automation needs to be adopted as a total process, not a bit part player. Historically automation has focussed on the User Interface, which can be a start, but is often woefully lacking. Implementing an Automation Eco-System, sees automation drive through to the interface or service layer, enabling far higher reuse of automated scripts, encompasses the environment and the test data within it’s strategy, providing a robust, repeatable and reusable asset.
Don’t just automate the obvious. Automation is not a black box testing technique. Rather it is mirroring the development and building an exercise schedule for the code. Take your testing to the next level and realise the real benefits of a modern Automation Eco-system.
Mattias Ratert - Incremental Scenario Testing
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Top Chrome Extensions for Software Testing
Kanoah Tests is a test management tool that integrates seamlessly with JIRA. It allows coordinating all test management activities like planning, authoring, execution, tracking and reporting from within JIRA. Key features include native JIRA integration, reusable test cases across projects, powerful REST API, and out-of-the-box reports for real-time insights. Reviews praise its simple and elegant solution for linking tests between projects without needing to learn new tools or switch contexts.
Business value assurance / Advanced DWH testing
The document discusses challenges faced during data warehouse testing at different stages of the software development life cycle. It addresses issues like lack of skilled testers, insufficient test data, poor understanding of requirements, time constraints, and challenges of testing different phases like ETL and performance testing. It also asks questions about tools that can be used for testing data quality, completeness, reconciliation and bulk data as well as performance analysis.
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!
EuroSTAR Software Testing Conference 2008 presentation on Tester Needed? No Thanks, We Use MBT! by Elise Greveraars. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Testing Frameworks And Methodologies
The document discusses various testing frameworks and methodologies for websites. It describes different types of tests like card sorting, wireframe testing, design testing, and usability testing. It emphasizes the importance of testing websites on multiple browsers and computers. Usability testing involves measuring efficiency, accuracy, recall, and emotional response. The document also outlines tools for testing like the W3C validation services for HTML, CSS, and links. It stresses testing with real users throughout the design and development process.
Software Testing Interview Q&A – part 1
The document provides sample answers to common software testing interview questions. It begins with introducing oneself, including education, experience, and strong points. It then discusses responsibilities as a QA engineer or leader. Other questions and answers cover strong and weak points, reasons for changing jobs, knowing when testing is enough, when testing should stop, estimating testing time, challenges faced, and achievements. The document provides guidance on working under pressure.
Defect prevention techniques
The document is an introduction to a book about software defect prevention techniques. It provides an example project with 5000 lines of Java source code from 2004 that was analyzed using various static analysis tools. The tools uncovered over 1120 code violations and 121 design violations. The document then provides a detailed 37 video course on software engineering from IIT Bombay that covers topics like requirements engineering, formal specification, system modeling, design patterns, testing, and project management which provide a solid theoretical foundation for applying software defect prevention techniques. Finally, it summarizes the contents of each video in the course.
From Defect Reporting To Defect Prevention
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
More Related Content
What's hot
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
TDD involves writing tests before writing code to satisfy requirements. The document discusses TDD, providing:
1. An overview of the TDD process and definitions of its key steps - make a test, make it fail, make it pass.
2. An example walking through writing a test for an "easy button" and implementing the code to pass the test.
3. Reasons for using TDD, including improved code quality, design, discipline, and documentation from maintaining an automated test suite.
Myths and reality about software testing
Most of the people might say that software test engineers do not write code. Testers normally need completely different skill set which could be a mix of Java, C, Ruby, and Python.
That is not all you require to be a successful tester. A tester requires having a good knowledge of the software manuals and automation tools.
Depending on the complexity of a project, a software testing engineer may write more complicated code than the developer.
Agile Testing - Not Just Tester’s Story _ Dang Thanh Long
This topic will focus on how testing should be understood/supported/changed for all levels including customer, executives and development team (Dev, QA…) during adopting Agile methodologies, especially testing mindset. Besides that, this topic could also cover some lessons learnt from some Agile testing practices.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Achieve Intelligent Test Execution: Strategies for Streamlining Regression Te...
If you ask a business leader which features in a given software release are most critical (and which potential failures keep them up at night), chances are they'll be related to the UI. But with many testing teams spending up to 80% of their time on regression testing, how can you make time for the resource-intensive tests that verify these high business value features? In this webinar, Adam Satterfield will share strategies for optimizing the plan and build phases of a project to eliminate redundancy and free up time for the tests that matter most to the business, including:
The questions you should ask business leaders before the build begins
Why it's critical for testers to give feedback during build output and unit test reviews
How to segment UI tests to focus on validating business-critical features first
Why adopting this approach can turn good test engineers into great ones -- and improve manual testers' technical aptitude
Istqb intro with question answer for exam preparation
The document provides an overview of software testing concepts including definitions of software testing, who can perform testing, common terminology, the software development life cycle (SDLC), testing methods and levels, and more. It defines software testing as the process of comparing expected and actual results to identify defects. It outlines the typical stages of the SDLC as initial, analysis, design, coding, testing, and delivery/maintenance phases. It also describes black box, white box, and grey box testing methods and the five levels of testing: unit, module, integration, system, and acceptance.
38475471 qa-and-software-testing-interview-questions-and-answers
The document discusses software testing concepts including:
- Quality assurance ensures processes are established to produce products that meet specifications.
- Testing determines if a product meets requirements and identifies failures to meet requirements.
- A test plan is written by the lead tester and includes the testing strategy, resources, and plans. It outlines test cases and procedures to validate software meets specifications.
- Testing begins in the define system phase to ensure requirements are testable, and continues through subsequent phases including product testing, acceptance testing, and deployment. Documentation and repeatable processes are critical to quality assurance.
Wim Demey - Regression Testing in a Migration Project
EuroSTAR Software Testing Conference 2009 presentation on Regression Testing in a Migration Project by Wim Demey. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Software testing interview Q&A – Part 2
This is collection of question & answer in software testing interview job. Part 2 with 10 questions and answers.
This is designed by Khoa Bui, which owner of http://www.testing.com.vn site
Automation testing in Agile project
The document summarizes best practices for test automation, including:
- Unit tests should be automated as the first step and follow naming conventions.
- Integration and performance tests require grouping, isolation, and handling test data issues.
- UI tests can be automated with Selenium and integrated into the build pipeline.
- Automated test data, code, and plan generation may be useful once a project's structure stabilizes.
- Automation aims to provide transparency, improve skills, and reduce manual work over time through a smarter approach.
Test Design with Action-based Testing Methodology - Ngo Hoang Minh
Test Design with Action-based Testing Methodology - Ngo Hoang MinhHo Chi Minh City Software Testing Club
Nowadays in IT market, most of enterprises are trying to adopt agile and DevOps methodology to meet the time-to-market expectations and continue satisfying their customers. As the result, continue deploying new applications are become challenges for any software development teams.
During the development cycles, several questions has been identified and one of the most interesting questions is How to fit automated tests into agile projects because within agile sprints, there is simply not enough time to automate the set of tests?
Action Based Testing (ABT) methodology is becoming a solution to help you achieve your expectations on automated test coverage within the Agile iterations/sprints.
ABT uses a modular keyword-driven approach which tests are organized in test modules and are built up of sequences of actions. Well-defined test modules can provide a healthy framework for teams to work with, in particular if modules have a clear and unambiguous scope, the scope is well-differentiated from other test modules, and all test cases …within the test module reflect the scope.
A key differentiation is between business tests and interaction tests. Business tests have a business-oriented scope and should not contain UI details. Interaction tests focus on the interaction between the user (or another system) and the application.
This topic is about how to apply ABT methodologies into SDLC with some discussions on the three Holy Grail of test design approaches from Hans Buwalda. Rapid software testing
This document discusses an introduction to a class on rapid software testing. It states that the class aims to make students stronger, smarter and more confident testers by challenging them to think for themselves rather than simply listening to what the instructors say. The class can be beneficial for testers of all experience levels who want to improve at their work. Heuristics are discussed as techniques that can help substitute for complete analysis and involve guidewords, triggers, reframing ideas, and procedures to help solve problems.
Use Automation to Assist—Not Replace—Manual Testing
Automation is a powerful tool to help testing but too often it is used to replicate existing manual tests. This leads organizations to spend large amounts of time and money constantly updating flaky automated tests and test teams to suffer frustration from having to focus on activities that are not truly testing. This cost and frustration can be avoided by using automation as a tool to assist testing—not to replace tests. Jeffrey Martin shares some real-world examples of using automation to supplement testing by leveraging its true value—the replication and repetition of tasks instead of tests. Examples are drawn from several testing teams, as well as his own. Jeffrey explores what kinds of tasks are the best fit for automation, identifies which tasks are better left to testers, and provides examples of melding task automation and manual tests together. Jeffrey discusses how organizations have introduced these concepts to maximize adoption and team buy-in. Leave with a different view of automation and ideas on how to best use this powerful tool to supplement actual tests seamlessly in your own team.
The Leaders Guide to Getting Started with Automated Testing
Conventional testing is yesterday’s news, is required but needs the same overhaul that has happened in development. It needs to be a slicker operation that really identifies the risk associated with release and protects the business from serious system failure. The only way to achieve this is to remove the humans, they are prone to error, take a long time, cost a lot of money and don’t always do what they are told.
Automation needs to be adopted as a total process, not a bit part player. Historically automation has focussed on the User Interface, which can be a start, but is often woefully lacking. Implementing an Automation Eco-System, sees automation drive through to the interface or service layer, enabling far higher reuse of automated scripts, encompasses the environment and the test data within it’s strategy, providing a robust, repeatable and reusable asset.
Don’t just automate the obvious. Automation is not a black box testing technique. Rather it is mirroring the development and building an exercise schedule for the code. Take your testing to the next level and realise the real benefits of a modern Automation Eco-system.
Mattias Ratert - Incremental Scenario Testing
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Top Chrome Extensions for Software Testing
Kanoah Tests is a test management tool that integrates seamlessly with JIRA. It allows coordinating all test management activities like planning, authoring, execution, tracking and reporting from within JIRA. Key features include native JIRA integration, reusable test cases across projects, powerful REST API, and out-of-the-box reports for real-time insights. Reviews praise its simple and elegant solution for linking tests between projects without needing to learn new tools or switch contexts.
Business value assurance / Advanced DWH testing
The document discusses challenges faced during data warehouse testing at different stages of the software development life cycle. It addresses issues like lack of skilled testers, insufficient test data, poor understanding of requirements, time constraints, and challenges of testing different phases like ETL and performance testing. It also asks questions about tools that can be used for testing data quality, completeness, reconciliation and bulk data as well as performance analysis.
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!
EuroSTAR Software Testing Conference 2008 presentation on Tester Needed? No Thanks, We Use MBT! by Elise Greveraars. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Testing Frameworks And Methodologies
The document discusses various testing frameworks and methodologies for websites. It describes different types of tests like card sorting, wireframe testing, design testing, and usability testing. It emphasizes the importance of testing websites on multiple browsers and computers. Usability testing involves measuring efficiency, accuracy, recall, and emotional response. The document also outlines tools for testing like the W3C validation services for HTML, CSS, and links. It stresses testing with real users throughout the design and development process.
Software Testing Interview Q&A – part 1
The document provides sample answers to common software testing interview questions. It begins with introducing oneself, including education, experience, and strong points. It then discusses responsibilities as a QA engineer or leader. Other questions and answers cover strong and weak points, reasons for changing jobs, knowing when testing is enough, when testing should stop, estimating testing time, challenges faced, and achievements. The document provides guidance on working under pressure.
What's hot (20)
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
Agile Testing - Not Just Tester’s Story _ Dang Thanh Long
Agile Testing - Not Just Tester’s Story _ Dang Thanh Long
Achieve Intelligent Test Execution: Strategies for Streamlining Regression Te...
Achieve Intelligent Test Execution: Strategies for Streamlining Regression Te...
Istqb intro with question answer for exam preparation
Istqb intro with question answer for exam preparation
38475471 qa-and-software-testing-interview-questions-and-answers
38475471 qa-and-software-testing-interview-questions-and-answers
Wim Demey - Regression Testing in a Migration Project
Wim Demey - Regression Testing in a Migration Project
Test Design with Action-based Testing Methodology - Ngo Hoang Minh
Test Design with Action-based Testing Methodology - Ngo Hoang Minh
Use Automation to Assist—Not Replace—Manual Testing
Use Automation to Assist—Not Replace—Manual Testing
The Leaders Guide to Getting Started with Automated Testing
The Leaders Guide to Getting Started with Automated Testing
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!
Viewers also liked
Defect prevention techniques
The document is an introduction to a book about software defect prevention techniques. It provides an example project with 5000 lines of Java source code from 2004 that was analyzed using various static analysis tools. The tools uncovered over 1120 code violations and 121 design violations. The document then provides a detailed 37 video course on software engineering from IIT Bombay that covers topics like requirements engineering, formal specification, system modeling, design patterns, testing, and project management which provide a solid theoretical foundation for applying software defect prevention techniques. Finally, it summarizes the contents of each video in the course.
From Defect Reporting To Defect Prevention
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
Defect management using kanban
Lightweight approach to defect management using Kanban. Presentation was originally for a build team to manage build requests, please excuse any typos which still references the build process.
Defect Analytics & Statistical Trends
This document introduces defect analytics and statistical trends (DAST), a quality model for defect management and measurement. DAST focuses on defect reporting, resolution, and generating reports from a defect data mart to analyze metrics and trends. These reports are used to guide defect prevention, improve quality and productivity, and support go/no-go decisions for releases.
Advanced Defect Management
This document discusses IBM's approach to advanced defect management. It introduces two of IBM's analytical predictive capabilities: the IBM Defect Reduction Method, which classifies and analyzes defects to find and fix them early, and the Test Planning and Optimization Workbench, which delivers an optimized test strategy and project planning through defect predictions. Using these capabilities, IBM has achieved substantial gains for clients such as reduced costs, accelerated schedules, improved quality, and lower risks. The document provides examples of how IBM has helped validate testing estimates and select accelerators for clients to reduce production defects.
Defect prevention
This document discusses defect prevention as a way to reduce costs and enhance quality in software development. It notes that preventing defects is better than fixing them later. The key points made include:
- Defects are imperfections that cause software to fail to meet expectations. Most defects are introduced early but found later in the process.
- Defect prevention identifies root causes through analysis of past defects to prevent recurrences. This improves productivity and reduces rework.
- Fixing defects gets significantly more expensive later in the process, from design to maintenance. Methods of prevention include reviews, inspections, walkthroughs, logging defects, and root cause analysis techniques like Pareto analysis and fishbone diagrams.
-
defect tracking and management
The document discusses defect tracking and management. It provides details on defect identification, reporting, tracking, resolution and using defect information to improve processes. A recommended structure is given for defect reports, including title, description, steps to reproduce, actual and expected results. Examples of a defect report and tracking sheet in Excel are also shown. The defect management process involves executing tests, logging discrepancies, reviewing with developers, assigning defects, retesting after fixes, and closing defects when resolved.
Defect analysis and prevention methods
The document discusses defect analysis and prevention. It defines key terms like errors, defects, and failures. It describes the defect analysis procedure which includes forming a causal analysis team to identify root causes of defects so they can be prevented. The team proposes actions, while an action team implements solutions. Data on defect types and trends is analyzed to prioritize issues. Tools like fishbone diagrams may be used to sort contributing factors. The goal is to systematically eliminate common causes of defects.
Viewers also liked (8)
Similar to Darshan Desai - Virtual Test Labs,The Next Frontier - EuroSTAR 2010
Improving Software Development Across the Lifecycle with Microsoft Visual Stu...
This document discusses how Microsoft Visual Studio 2010 can help improve software development across the lifecycle. It highlights features that help developers understand existing systems through architectural visualization and layer diagrams, eliminate bugs using IntelliTrace for debugging, and streamline processes with improved agile support, reporting, and SharePoint dashboards for increased visibility and risk reduction. A Q&A section is included at the end.
No More No Repro
Microsoft's Visual Studio 2010 and Team Foundation Server 2010 include many new and improved testing capabilities that aim to break down silos between development and testing teams. Key features include innovative test case management, automated build-deploy-test workflows, test lab management for virtual environments, rich bug filing capabilities, and tools to help developers identify and fix issues early like IntelliTrace and Coded UI testing. The integrated offerings are designed to align quality assurance more closely with the development lifecycle and enable highly leveraged QA teams.
Visual Studio ALM and DevOps Tools Walkthrough
If you're considering moving to Team Foundation Server or Visual Studio Team Services, this deck will walk you through the highlights, of which there are a TON!
Designing Self-maintaining UI Tests for Web Applications
This document discusses the challenges of test automation and proposes some solutions. It notes that products are constantly changing, developers do not always communicate changes, and testers spend significant time fixing broken tests rather than writing new ones. It proposes moving testing earlier in the process, embedding testers with developers, and using automation to prevent broken builds. Moving to more automated and maintainable tests over time can reduce maintenance costs and give testers a better understanding of how software is developed. Key steps include treating test automation as software development, improving presentation layer consistency, and better communication between testers and developers.
DevOps beyond the Tools
DevOps is mainstream - at least the tools, the automation and the metrics. But what happened to DevOps Culture? Does it still matter? If yes - how do we achieve it?
Putting the DOT in .NET - Dev/Ops/Test
A high level tour of what DevOps is and how the tooling from Microsoft aligns & assists an organization move to DevOps.
This session was presented as part of the Microsoft South Africa Dev Day roadshow in March 2015.
More info at: http://www.sadev.co.za/content/slides-my-devday-march-2015-talks
Visual Studio Enterprise 2015 Overview atidan
This huge transformation for Visual Studio to enable the creation of any application is two-fold, on the server and on the client:
On the client side, Visual Studio 2015 provides a solution to create first-class applications for any device including iOS, Android and Windows.
On the server side, just like the rest of the Microsoft platform, Visual Studio is embracing Linux and provides a development environment for creating server applications that run on Linux.
We will also support major platforms in our ALM tooling – with features like cross-platform build and heterogenous release management offered by TFS 2015 and Visual Studio Online
What about “every developer”?
Last year, at our Connect() event we made a significant announcement targeted at individual developers, such as students, start-ups, small businesses.
With VS Community, eligible developers can use a full IDE, equivalent to the current VS Professional edition, for creating applications across the cloud and devices – for free!
But what about Enterprises?
With Visual Studio 2015, we are making it easier for enterprises to acquire and use Visual Studio, with a simpler model that will give developers working in organizations easier and more affordable access to Visual Studio. In this new model, we have introduced a new edition of Visual Studio called Visual Studio Enterprise.
Ontwikkelstraat in de Cloud: ALM en Azure een krachtige combinatie
De Cloud is allang geen hype meer, maar een concept waar vroeg of laat alle bedrijven mee te maken krijgen. Ook Microsoft geeft met haar Cloud First visie aan dat uiteindelijk veel software en diensten zullen verschuiven naar de Cloud.
Een van de vlakken waarop met de inzet van cloud technologie veel winst valt te behalen is Application Lifecycle Management (ALM). Het eerste waaraan gedacht wordt is uiteraard Visual Studio Online. Het SaaS alternatief van Microsoft voor de on-premise Team Foundation Server. Maar met Microsoft Azure zijn er nog veel meer voordelen te behalen op het gebied van virtuele ontwikkel omgevingen en flexibele development en test omgevingen.
Op 7 oktober organiseren wij een online seminar over dit onderwerp. Onze Microsoft MVP's voor Microsoft Azure en Application Lifecycle Management bundelen hun krachten om u binnen een uur mee te nemen in de mogelijkheden van ontwikkelen in de Cloud met Microsoft Azure en Visual Studio Online. Tevens zullen we kort toelichten welke voordelen u met uw bestaande MSDN abonnement direct al kunt benutten.
Deze slidedeck bevat een selectie van de sheets die tijdens het webinar op 7 oktober gebruikt zullen worden.
Bent u verantwoordelijk voor de ontwikkeling van software binnen uw organisatie, dan mag u dit webinar niet missen.
A Lap Around Visual Studio 2010
The document summarizes the key capabilities of Microsoft's Visual Studio 2010 and Team Foundation Server for improving the software development lifecycle. It discusses how the tools can help ensure quality code, enhance team collaboration through integration, and allow teams to spend more time creating code rather than debugging it. The tools provide capabilities for version control, build automation, testing, project management, code analysis, modeling, and more to help deliver projects on time and on budget.
Microservices Architecture: Nirvana or Nightmare
Microservice oriented architecture is very fashion. It is very easy to find posts describing success story with this kind of architecture. However, this kind of architecture comes with a set of traps and assume a lot of things about your company's IT.
In this task I will show in which context this kind of architecture makes sense, the challenges coming with it, the kind of data architecture it implies and the most mature existing stacks to work with.
Transcript available http://francesbagual.net/2015/11/03/Microservices-architecture-Nirvana-or-Nightmare-part-i.html
Arquitetura orientada a micro serviços: Nirvana ou pesadelo?
Arquitetura orientada a micro serviços está na moda. É fácil achar artigos falando bem desse tipo de arquitetura com todos os seus beneficio. Porém, esse tipo de arquitetura vem com seu conjunto de armadilhas e assume muitas coisas sobre a TI da sua empresa. <br><br>
Nessa palestra mostrarei em quais contextos esse tipo de arquitetura faz sentido, os desafios que vem com ela, o tipo de arquitetura de dados que ela implica e as stacks mais maduras para trabalhar com micro serviços.
This isn't what you think it is
Wintellect provides consulting and training services focused on Microsoft technologies. It was founded by top Microsoft experts and offers a variety of services including architecture design, software development, debugging, and database design. Wintellect's training courses cover current and emerging technologies and are taught by industry leaders. The training can be done onsite, virtually, or on-demand to provide flexibility.
The state of testing @ Microsoft
State of testing at Microsoft focuses on quality, collaboration throughout the development lifecycle. Microsoft provides tools to empower testing, feedback, and monitoring including test case management, manual and exploratory testing, browser-based testing, feedback management, quality dashboards, lab management, release management, and application insights. The tools are designed to put quality at the center and close the loop between development and operations.
STAREAST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
Step 1 discusses work management in Visual Studio/TFS 2010, including hierarchical work management, improved dashboards and reports, and Excel integration. Step 2 covers defining and reporting on what is considered "done". Step 3 discusses automated builds, including build reports and associating work items. Step 4 focuses on manual testing tools like Microsoft Test Manager for test planning, management, and bug filing.
Improving developer tester collaboration with microsoft visual studio 2010
A presentation I gave at the VS 2010 launch on the new features of VS2010 that improve developer/tester collaboration
Visual Studio 2015 / Visual Studio Team Services Overview
Visual Studio 2015 provides tools to help developers at every stage of development. It includes features like IntelliTest to automatically generate unit tests, Code Maps to visualize code relationships, and IntelliTrace to debug issues without setting breakpoints. Visual Studio Team Services offers agile planning tools, release management to automate deployments, and cloud environments for flexible development and testing. The presentation provides an overview of the developer tools and features in Visual Studio 2015 and Visual Studio Team Services.
STARWEST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
Using Microsoft Test Manager, Visual Studio 2010, and TFS 2010 can improve software quality through a 7 step approach: 1) Work management, 2) Defining what "done" means, 3) Automated builds, 4) Manual and automated testing tools, 5) Developer quality tools, 6) Lab management, and 7) Working smart. These tools provide an integrated environment for managing work, automating builds, facilitating manual and automated testing, and providing virtual test environments to improve efficiency and quality.
Microsoft DevOps Solution - DevOps
Slides I have used to have a customer engagement on DevOps and show what Microsoft has invested in DevOps.
STARWEST 2010 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
Using Visual Studio 2010, teams can improve software quality through 7 steps: 1) work management with hierarchical tasks and improved reporting; 2) defining "done" with dashboards; 3) automated builds with traceability from development to testing; 4) manual and automated testing tools; 5) developer quality tools to find and fix bugs early; 6) test lab management with virtual environments; and 7) continuous improvement through an integrated and productive environment.
Easily Create Scalable Automation using Selenium
We were delighted to be at STAREAST again, one of the longest-running and most respected conferences on software testing and quality assurance. Archie Roboostoff ran a session on how to easily create Scalable Test Automation using Selenium and here are his charts. To find out more about how we can help go to https://www.microfocus.com/products/silk-portfolio/silk-webdriver/
Similar to Darshan Desai - Virtual Test Labs,The Next Frontier - EuroSTAR 2010 (20)
Improving Software Development Across the Lifecycle with Microsoft Visual Stu...
Improving Software Development Across the Lifecycle with Microsoft Visual Stu...
Designing Self-maintaining UI Tests for Web Applications
Designing Self-maintaining UI Tests for Web Applications
Ontwikkelstraat in de Cloud: ALM en Azure een krachtige combinatie
Ontwikkelstraat in de Cloud: ALM en Azure een krachtige combinatie
Arquitetura orientada a micro serviços: Nirvana ou pesadelo?
Arquitetura orientada a micro serviços: Nirvana ou pesadelo?
STAREAST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
STAREAST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
Improving developer tester collaboration with microsoft visual studio 2010
Improving developer tester collaboration with microsoft visual studio 2010
Visual Studio 2015 / Visual Studio Team Services Overview
Visual Studio 2015 / Visual Studio Team Services Overview
STARWEST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
STARWEST 2011 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
STARWEST 2010 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
STARWEST 2010 - 7 Steps To Improving Software Quality using Microsoft Test Ma...
More from TEST Huddle
Why We Need Diversity in Testing- Accenture
In this webinar Rasa (Testing capability lead for Denmark) and Matthias (EALA Testing capability lead) will share some of their own experiences why diversity matters, give insights into how Accenture as a global firm is promoting diversity and how we are in the process of changing our attitudes and processes to make all of this sustainable
Keys to continuous testing for faster delivery euro star webinar
Your business needs to deliver faster. To accommodate, Development needs to introduce fewer changes but in a much more frequent cadence. This creates a challenge for test teams to keep up with the rapid pace of change without compromising on quality. Automation is paramount to the success or failure of Continuous Delivery, and Continuous Testing enables early and frequent quality feedback throughout the CI/CD pipeline.
In this webinar, Eran & Ayal will explore how to implement Continuous Testing to ensure high quality releases in a Continuous Delivery environment; including what to test and when to automate new functionality in order to optimize your efforts.
Why you Shouldnt Automated But You Will Anyway
The document discusses automation in software testing. It begins by outlining common claims made about the benefits of automation, such as saving time and improving quality, but argues that these claims often don't hold true. Automation does not inherently save time, guarantee quality, or reduce resources needed. It also does not always save money when development, maintenance, and infrastructure costs are considered. The document provides a formula for determining when automation is worthwhile based on how many times a test case would need to be rerun manually. It concludes by acknowledging that, despite these drawbacks, organizations will still automate testing because it is exciting, managers demand it, and it benefits careers.
Being a Tester in Scrum
In this webinar Carsten will explore the role of the tester in a Scrum team. He will examine where the tester play an important role in Scrum and how you can contribute to a teams performance.
Leveraging Visual Testing with Your Functional Tests
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability
Using Test Trees to get an Overview of Test Work
In this webinar, Anne Mette will inspire you to use Test Trees for your testing and highlight how it will make your tests more clear and visible
Big Data: The Magic to Attain New Heights
This document discusses how big data and data science can be used to attain new heights, likening it to magic. It provides an overview of Ken Johnston's background and experiences in data science. It then discusses six keys to a "big" magic show with big data: trying multiple times, addressing issues with over-counting, experimentation techniques like A/B testing, infrastructure for big data, tools and skills, and security, privacy and fraud protection. The document emphasizes the importance of an assistant to help the data scientist or data engineer with various tasks.
Will Robots Replace Testers?
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
TDD For The Rest Of Us
The document discusses Test Driven Development (TDD) and Test Driven Design. It uses the analogy of building a lightsaber and later a Death Star to illustrate the TDD process and benefits. Some benefits mentioned are better test coverage, less debugging, and better design. The document provides tips for practicing TDD including planning ahead, defining boundaries, taking small steps to pass each test, and maintaining discipline. It emphasizes trying TDD in a team and considering Behavior Driven Development (BDD) as well.
Scaling Agile with LeSS (Large Scale Scrum)
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Creating Agile Test Strategies for Larger Enterprises
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
Is There A Risk?
3 key takeaways
- Do you know the meaning of your organisation, system, product?
- Can you deliver the important risks right away?
- How can you communicate about the (process and product) risks your dealing with?
View Webinar recording: https://huddle.eurostarsoftwaretesting.com/resource/test-management/is-there-a-risk/
Are Your Tests Well-Travelled? Thoughts About Test Coverage
This document summarizes a presentation on test coverage given by Dorothy Graham. It uses an analogy of travel to different locations to explain what test coverage means and some caveats. Coverage refers to the relationship between tests and the parts of a system being tested, but achieving 100% coverage does not mean everything is tested. There are four caveats discussed: coverage only measures one aspect of testing, a single test can achieve coverage, coverage does not indicate quality, and it only applies to the existing system not missing pieces. The key recommendation is to ask "coverage of what?" when the term is used rather than assuming more coverage is always better.
Growing a Company Test Community: Roles and Paths for Testers
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
Do we need testers on agile teams?
It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.
http://huddle.eurostarsoftwaretesting.com/resource/webinar/need-testers-agile-teams/
How to use selenium successfully
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Testers & Teams on the Agile Fluency™ Journey
The document discusses the Agile Fluency model, which aims to help teams and testers improve their agile skills and practices over time. It describes a pathway with increasing levels of fluency that provide more benefits, including delivering value, optimizing value, and innovating. Reaching higher levels requires investments in training, coaching, and changing team structures and roles. The model can help organizations determine what level of fluency they need and what investments are required for testing teams to operate at that level.
Practical Test Strategy Using Heuristics
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Thinking Through Your Role
Key Takeaways:
- A diagramming method that helps discuss roles
- A one page analysis heuristic for roles
- Why roles matter on projects
https://huddle.eurostarsoftwaretesting.com/resource/people-skills/thinking-through-your-role/
Using Selenium 3 0
Key Takeaways:
- What will this release contain
- What impact will it have on your test runs
- How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests
- Looking forward, when will the W3C spec be complete
- What can we expect from Selenium 4
https://huddle.eurostarsoftwaretesting.com/
More from TEST Huddle (20)
Keys to continuous testing for faster delivery euro star webinar
Keys to continuous testing for faster delivery euro star webinar
Leveraging Visual Testing with Your Functional Tests
Leveraging Visual Testing with Your Functional Tests
Creating Agile Test Strategies for Larger Enterprises
Creating Agile Test Strategies for Larger Enterprises
Are Your Tests Well-Travelled? Thoughts About Test Coverage
Are Your Tests Well-Travelled? Thoughts About Test Coverage
Growing a Company Test Community: Roles and Paths for Testers
Growing a Company Test Community: Roles and Paths for Testers
Recently uploaded
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
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
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
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…
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.
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.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
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.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
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.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
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.
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.
Recently uploaded (20)
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 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...
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
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...
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Darshan Desai - Virtual Test Labs,The Next Frontier - EuroSTAR 2010
- 1. Virtual Test Labs The next frontier DarshanDesai Program Manager Visual Studio -Test and Lab Management Microsoft India, Hyderabad darshand@microsoft.com| http://blogs.msdn.com/b/lab_management
- 2. Meet Ellen
- 6. Wants to help ship "great" software
- 7. Ellen‟s woes
- 8. Environment setup is painful
- 10. Cannot catch up with development
- 12. What if?
- 13. Environment setup is „quick and easy‟
- 14. No more “no-repro” bugs
- 15. Development and testing work hand in hand
- 17. Demo -Virtual labsDemo Virtual lab in action
- 19. Integration
- 20. Cloning VMs without conflicts
- 21. Rewinding clock with snapshots
- 22. Virtual labs empower Ellen
- 23. Save time and increase productivity
- 26. Help ship "great" software
- 28. Questions??
- 29. Darshan Desai Email:darshand@microsoft.com Blog: http://blogs.msdn.com/b/lab_management Web: http://www.microsoft.com/visualstudio/en-us/products Contacts