One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides examples of typical requirements and explains how to improve them using the Easy Approach to Requirements Syntax (EARS). EARS provides a simple yet powerful method of capturing the nuances of functional requirements. John explains that you need to identify two distinct types of requirements. Ubiquitous requirements state a fundamental property of the software that always occurs; non-ubiquitous requirements depend on the occurrence of an event, error condition, state, or option. Learn and practice identifying the correct requirements type and restating those requirements with the corresponding syntax. Join John to find out what’s wrong with the requirements statement—“The software shall warn of low battery”—and how to fix it.
EARS: The Easy Approach to Requirements SyntaxTechWell
One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides examples of typical requirements and explains how to improve them using the Easy Approach to Requirements Syntax (EARS). EARS provides a simple yet powerful method of capturing the nuances of functional requirements. John explains that you need to identify two distinct types of requirements. Ubiquitous requirements state a fundamental property of the software that always occurs; non-ubiquitous requirements depend on the occurrence of an event, error condition, state, or option. Learn and practice identifying the correct requirements type and restating those requirements with the corresponding syntax. Join John to find out what’s wrong with the requirements statement—The software shall warn of low battery—and how to fix it.
This ppt covers the following
A strategic approach to testing
Test strategies for conventional software
Test strategies for object-oriented software
Validation testing
System testing
The art of debugging
EARS: The Easy Approach to Requirements SyntaxTechWell
One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides examples of typical requirements and explains how to improve them using the Easy Approach to Requirements Syntax (EARS). EARS provides a simple yet powerful method of capturing the nuances of functional requirements. John explains that you need to identify two distinct types of requirements. Ubiquitous requirements state a fundamental property of the software that always occurs; non-ubiquitous requirements depend on the occurrence of an event, error condition, state, or option. Learn and practice identifying the correct requirements type and restating those requirements with the corresponding syntax. Join John to find out what’s wrong with the requirements statement—The software shall warn of low battery—and how to fix it.
This ppt covers the following
A strategic approach to testing
Test strategies for conventional software
Test strategies for object-oriented software
Validation testing
System testing
The art of debugging
How To Write A Test Case In Software Testing | EdurekaEdureka!
YouTube Link: https://youtu.be/KxelISpFqOY
(** Test Automation Masters Program: https://www.edureka.co/masters-progra... **)
This Edureka PPT on "Test Case in Software Testing" will give you in-depth knowledge on how to write a Test Case in Software Testing. The following are the topics covered in the session:
Software Testing Documentation
Test Case in Software Testing
Test Case Format
Test Case Design Technique
Test Case Guidelines
Demo: How to write a test case?
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Objectives:
1. To understand the different processes in the realm of ‘Requirements Engineering’.
2. To see the challenges in requirements development and the importance of getting requirements right in an IT project.
3. To understand the different techniques used in different phases and processes of requirements development and management.
The reality is that technology is complicated. As testers, we are challenged with complicated problems that need solving. Andy Glover presents a hands-on workshop that describes a new way of looking at testing problems and ideas. Andy demonstrates how thinking with pictures can help testers discover and develop new ideas, solve problems in unexpected ways, and dramatically improve their ability to share their insights with others. Andy shows how to clarify a problem or sell an idea by visually breaking it down using a set of visualization tools including mind maps, work flows, and powerful but simple visuals to communicate complex messages. You don’t need to know how to draw to attend this workshop. Although we are naturally creative, sometimes it takes effort to develop those skills. Join Andy to learn how to apply visual solutions to our everyday software testing challenges.
Balancing the Crusty and Old with the Shiny and NewTechWell
In his journeys, Bob Galen has discovered that testing takes on many forms. Some organizations have no automated tests and struggle to run massive manual regression tests within very short iterative releases. Other organizations are going “all in”―writing thousands of acceptance tests in Gherkin. The resulting imbalance in their testing approaches undermines an organization’s efficiency, effectiveness, and delivery nimbleness. Bob shares ideas to bring balance to testing. He explores the choices: manual vs. automated testing, designed and scripted test cases vs. exploratory tests, and thoroughly planned test projects vs. highly iterative reactive ones. Bob describes how to balance traditional test leadership with an iterative and whole team view to add value. And finally, he explores the balance of the gatekeeper vs. leading the collaboration with stakeholders to find the right requirements that solve their problems. Take away a strategic approach to structure your testing and a renewed understanding of how testing fits into a healthy and balanced culture.
How To Write A Test Case In Software Testing | EdurekaEdureka!
YouTube Link: https://youtu.be/KxelISpFqOY
(** Test Automation Masters Program: https://www.edureka.co/masters-progra... **)
This Edureka PPT on "Test Case in Software Testing" will give you in-depth knowledge on how to write a Test Case in Software Testing. The following are the topics covered in the session:
Software Testing Documentation
Test Case in Software Testing
Test Case Format
Test Case Design Technique
Test Case Guidelines
Demo: How to write a test case?
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Objectives:
1. To understand the different processes in the realm of ‘Requirements Engineering’.
2. To see the challenges in requirements development and the importance of getting requirements right in an IT project.
3. To understand the different techniques used in different phases and processes of requirements development and management.
The reality is that technology is complicated. As testers, we are challenged with complicated problems that need solving. Andy Glover presents a hands-on workshop that describes a new way of looking at testing problems and ideas. Andy demonstrates how thinking with pictures can help testers discover and develop new ideas, solve problems in unexpected ways, and dramatically improve their ability to share their insights with others. Andy shows how to clarify a problem or sell an idea by visually breaking it down using a set of visualization tools including mind maps, work flows, and powerful but simple visuals to communicate complex messages. You don’t need to know how to draw to attend this workshop. Although we are naturally creative, sometimes it takes effort to develop those skills. Join Andy to learn how to apply visual solutions to our everyday software testing challenges.
Balancing the Crusty and Old with the Shiny and NewTechWell
In his journeys, Bob Galen has discovered that testing takes on many forms. Some organizations have no automated tests and struggle to run massive manual regression tests within very short iterative releases. Other organizations are going “all in”―writing thousands of acceptance tests in Gherkin. The resulting imbalance in their testing approaches undermines an organization’s efficiency, effectiveness, and delivery nimbleness. Bob shares ideas to bring balance to testing. He explores the choices: manual vs. automated testing, designed and scripted test cases vs. exploratory tests, and thoroughly planned test projects vs. highly iterative reactive ones. Bob describes how to balance traditional test leadership with an iterative and whole team view to add value. And finally, he explores the balance of the gatekeeper vs. leading the collaboration with stakeholders to find the right requirements that solve their problems. Take away a strategic approach to structure your testing and a renewed understanding of how testing fits into a healthy and balanced culture.
Satisfying Auditors: Plans and Evidence in a Regulated EnvironmentTechWell
Testers want to be responsible and professional. However, they often come under pressure to comply with rules, standards, and processes that aren't always helpful. It's the price of keeping your auditors happy. But do you really know what auditors want? Are they all simply rule-obsessed, pedantic “little dictators”? James Christie shows why good auditors worry about risk—not rules. They want to explain the important risks to the people who lose sleep over them. James explains auditors' and regulators' attitudes toward risk and evidence. He shows that auditors' standards and governance models do have useful advice—knowledge that can help you choose the right testing approach for your project. James shows how to enlist smart auditors as valuable allies—and how to challenge the poor ones. Understanding auditors' needs will help you do better testing, at less cost. Wouldn't senior management and your stakeholders be interested in that?
Innovation Thinking: Evolve and Expand Your CapabilitiesTechWell
Innovation is a word frequently tossed around in organizations today. The standard clichés are do more with less and be creative. Companies want to be innovative but often struggle with how to define, implement, prioritize, and track their innovation efforts. Using the Innovation to Types model, Jennifer Bonine will help you transform your thinking regarding innovation and understand if your team and company goals match their innovation efforts. Learn how to classify your activities as "core" (to the business) or "context" (essential, but non-revenue generating). Once you understand how your innovation activities are related to revenue generating activities, you can better decide how much of your effort should be spent on core or context activities. Take away tools including an Innovation to Types model for classifying innovation, a Core and Context model to classify your activities, and a way to map your innovation initiatives to different contexts.
Playwriting, Imagination, and Agile Software Development … Oh My!TechWell
Agile practitioners are constantly striving to improve their processes and delivery to gain a competitive edge. To become a cross-functional T-shaped rock star, you have to be open to learning from other disciplines and adapting quickly. Tania Katan knows a little about crossing disciplines and adapting at a breakneck pace. She is a playwright by training who recently made the audacious leap into software. Tania helps you find your inner “T” so you will have the breadth and depth to take on the unpredictability of software development with the imagination and insights of a playwright. Exploring the parallels between agile principles and similar methodologies used by playwrights and performers, she will show you how to create tools that are more relevant and resonant to your intended audience. Tania shares stories and experiences about her own cross-functional team at Axosoft and how their commitment to being agile, conscious, and collaborative led her to co-create the internationally viral campaign #ItWasNeverADress.
The Doctor Is In: Diagnosing Test Automation DiseasesTechWell
When doing test automation, you sometimes notice that things are not working out as expected, but it’s not clear why. You are so caught up in the day-to-day work that you don't see the bigger picture. It’s like when you get sick―you know something is wrong, but you don’t know what. That’s the time to visit a doctor. Doctors diagnose diseases mainly by asking questions. First, they get a general idea of what’s wrong; then the questions become more and more specific; and in the end, they identify the disease and prescribe the appropriate cure. This method also works well for test automation. By first asking general questions, and then more and more specific ones, you can identify the disease (the issue) and then it’s relatively simple to select the most appropriate remedy. Seretta Gamba demonstrates this method with examples of common automation diseases and suggests the appropriate patterns to cure them.
Whether you are new to testing or looking for a better way to organize your test practices, understanding risk is essential to successful testing. Dale Perry describes a general risk-based framework—applicable to any development lifecycle model—to help you make critical testing decisions earlier and with more confidence. Learn how to focus your testing effort, what elements to test, and how to organize test designs and documentation. Review the fundamentals of risk identification, analysis, and the role testing plays in risk mitigation. Develop an inventory of test objectives to help prioritize your testing and translate them into a concrete strategy for creating tests. Focus your tests on the areas essential to your stakeholders. Execution and assessing test results provide a better understanding of both the effectiveness of your testing and the potential for failure in your software. Take back a proven approach to organize your testing efforts and new ways to add more value to your project and organization.
Executives’ Influence on Agile: The Good, the Bad, and the UglyTechWell
The evidence is in—and it's compelling. Well-executed agile practices can shorten software project schedules by 30 percent while cutting defects by 75 percent. However, many organizations struggle with agile adoption. And some of these struggles can be attributed to the executive leadership. In many cases, the "lead, follow, or get out of the way" attitude causes executives to try to lead when they should be following or getting out of the way. Drawing on his experiences with agile adoption at Synacor as it implements agile on an enterprise scale, Steve Davi illustrates how the executives on the ground can help or hurt agile adoption. Steve shares ways to turn those executive wolves into agile enablers as he describes the four critical actions that executives should take to support agile within their organization―define the vision, boundaries, and constraints; gain support and remove impediments; ensure openness and trust; and hold teams accountable.
Docker Containers in the Enterprise DevOps JourneyTechWell
As technology moves from being a cost-center to a revenue generator in nearly every business, technologists are expected to deliver more with fewer resources. DevOps enables this efficiency through improved collaboration between product management, development, release management, quality assurance, information security, and operations. However, Aater Suleman says that the challenge of incorporating DevOps into a business is no small task. Improving this collaboration requires cross-functional technologies that benefit all departments. By this definition, Docker may well be the most important tool in the DevOps toolbox as it allows empowering and permeable interfaces to be built between different departments throughout the DevOps loop. Aater explores both the Dev and Ops tracks of three companies and examines advantages that were achieved using Docker containers. He shows how Docker containers can work in environments from development to production and shares how this effort can be empirically tracked using five key performance indicators.
Is Agile the Prescription for the Public Sector’s IT Woes?TechWell
Information technology (IT) projects are notorious for exceeding budget and schedule estimates, and high visibility failures are common. IT projects in the public sector are particularly challenging. State, provincial, and federal governments worldwide have sponsored noteworthy disasters in the past twenty years. As agile methods have evolved, become more mainstream, and demonstrated their value in the private sector in the past decade, they are often cited as a remedy for the public sector’s IT misery. Payson Hall examines the gap between current public sector IT project challenges and the often-suggested agile solution. Payson explores the challenges to effective vendor-delivered public sector agile projects and possible responses to those challenges. He answers the questions: Is agile ready for large public sector projects? Is the public sector ready for agile? Leave with a better understanding of the problems public sector entities and vendors face and ideas for overcoming some of those barriers.
Getting Your Message Across: Communication Skills for TestersTechWell
Communication is at the heart of our profession. No matter how advanced our testing capabilities are, if we can’t convey our concerns in ways that connect with key members of the project team, our contribution is likely to be ignored. Because we act solely in an advisory capacity, rather than being in command, our power to exert influence is almost entirely based on our communication skills. With people suffering information overload and deluged with emails, it is more important than ever that we craft succinct and effective messages, using a range of communication modalities. Join Thomas McCoy as he draws on techniques from journalism, public relations, professional writing, psychology, and marketing to help you get your message across. Key themes include: non-verbal communication, presentation skills, persuasive writing, influencing skills, graphic communication, and communicating in teams and meetings. We will use a range of hands-on exercises to practice the concepts being discussed.
Business analysts, developers, and testers are sometimes not on the same page when it comes to test automation. When there is no transparency in test cases, execution, coverage, and data, review of automation by all stakeholders is difficult. Making automation scripts easily readable and writable allows stakeholders to better participate. Subodh Parulekar describes how his team dealt with these issues. Learn how they leveraged behavior-driven development (BDD) concepts and put a wrapper around their existing automation framework to make it more user-friendly with the easy to understand Given-When-Then format. Subodh discusses how his team implemented the new approach in four months to automate 700+ test cases. Now, test reports contain the actual Gherkin test step that passed or failed allowing any stakeholder to evaluate the outcome. Learn how stakeholders can rerun a failed test case from the reporting dashboard to determine if the failure is related to a synchronization, environmental, functional, or test data problem.
Test Automation Strategies for the Agile WorldTechWell
With the adoption of agile practices in many organizations, the test automation landscape has changed. Bob Galen explores current disruptors to traditional automation strategies, and discusses relevant and current adjustments you need to make when developing your automation business case. Open source tools are becoming incredibly viable and beat their commercial equivalents in many ways―not only in cost, but also in functionality, creativity, evolutionary speed, and developer acceptance. Agile methods have fundamentally challenged our traditional automation strategies. Now we must keep up with incremental and emergent systems and architectures and their high rates of change. Bob explores new automation strategies, examining strategies for both greenfield applications and those pesky legacy projects. Learn how to wrap a business case and communication plan around them so you get the support you need. Leave the workshop with a serious game-plan for delivering on the promise of agile test automation.
Build Your Open Source Performance Testing Platform in the CloudTechWell
Proprietary performance testing platforms can be complex, expensive, and difficult to scale. With the right approach, everything from continuous integration, to continuous deployment pipelines, to full-scale production loads can be supported, but a dizzying array of platforms, services, and approaches available in AWS and the open-source community must be navigated to arrive at solutions that work. Join Gopal Brugalette and explore how to build a performance testing platform in the cloud using open source tools. Gopal shares what he has learned from his failures and successes, explains why he's made the technical decisions he did, what he might have done differently, and how to create a roadmap for success. Attendees will gain insights into building a cloud-based performance testing platform using open-source and cloud tools to improve capabilities, increase efficiency, and reduce costs.
With the drive for continuous integration and delivery, the implications and approaches for designing more testable software are receiving substantial discussion and debate. What does testability really mean in practice? How do you take the idea of testability—how easy it is to test software—and put it into action through the different dimensions of designing and testing a real-world product? Nir Szilagyi recognizes that the challenges of difficult-to-test software can transform a testing cycle from a small automation and exploratory effort to a long struggle of test preparation, execution, and debugging. He says testability starts with software design, goes through implementation, and encompasses building modular software, abstraction, simplicity, clear data interface, separation of business logic into self-sustained entities, and more. On the technical side of testability, Nir explores ways quality engineers and leaders can influence testability from early development through deployment. From his experiences Nir shares real-life testability examples which touch on the human process of building software including the relationship between testers and developers.
IoT and Embedded Testing: A Roku Case StudyTechWell
With big hitters like Time Warner and HBO selectively testing Roku releases, testing these little boxes of joy is becoming more of a necessity in the IoT tester’s playbook. Join Rick Faulise as he shares the secrets of testing on a Roku device including how to get into the Roku interface and make it respond to your commands, how to select a broadcast environment for testing, and how to measure streaming performance. Take your IoT testing to the next level by understanding what special types of testing are unique to the Roku and other important considerations to keep in mind as you journey through the Brightscript SDK and Developer program, Telnet command prompts, and jailbreaking/hacking the Roku OS. Rick presents examples of testing on Roku devices and discusses how to decide what to test and in what order to test it. Take away two handouts: 1] how to jailbreak your Roku device, and 2] a comparison and contrast of testing on a Roku box, a Chromecast device, and an Amazon Fire TV stick.
Find Requirements Defects to Build Better SoftwareTechWell
Requirements defects are often the source of the majority of all software defects. Discovering and correcting a defect during testing is typically twenty-five times more expensive than correcting it during the requirements definition phase. Identifying and removing defects early in the software development lifecycle provides many benefits including reduced rework costs, less wasted effort, and greater team productivity. This translates into software projects that deliver the committed functionality on schedule, within budget, and with higher levels of customer satisfaction. John Terzakis shares powerful tips and techniques for quickly identifying requirements defects and providing feedback on how to improve them. Learn the ten attributes of a well-written requirement and how to detect various categories of requirements issues including ambiguity, passive voice, subjectivity, and missing event triggers. Using the concepts presented, John leads the analysis of a set of requirements. Leave with checklists that will make your requirements reviews more effective.
Threat Modeling for the Internet of ThingsEric Vétillard
A presentation made in several public events in 2015 about the threats related to the Internet of Things, and how modeling can be used as a way to manage mitigation methods.
BGOUG 2014 Decrease Your MySQL Attack SurfaceGeorgi Kodinov
Security is not a question of "if" but "when". People will hit at your server(s).
A smaller attack surface means they'll be more likely to miss too. And inflict less damage in general.
Let's find out some easy steps we can take to decrease MySQL's attack surface in a typical web setup
Quieting noisy neighbor with Intel® Resource Director TechnologyMichelle Holley
A typical computer server on the cloud hosted multiple VMs. Each VM hosted an independent application. The operation of a mixture of applications in cloud requires proper resource management and it's critical to QoS, this session is to study the impact of different neighbors on an application’s performance and to show how Intel® RDT can help to detect and mitigate a noisy-neighbor situation.
About the authors: Sunil is senior cloud performance engineer at Intel working on cloud performance and optimization for Oracle cloud. Prior to this he worked on service assurance and orchestration products for Openstack cloud. Sunil has 10+ years of experience working on different software products for server management. He holds Masters in Computer Science from IIT Chicago.
Khun Ban is a cloud performance engineer manager leading a team to optimize cloud performance and TCO. He has over twenty years of enterprise software development experience. His current focus is on providing customer with best cloud experience. He received his B.S. degree in Computer Science and Engineering from the University of Washington in 1995.
This is a practical introduction to the software failure modes effects analysis. The SFMEA is very effective but only if conducted properly and by the right people at the right time. Software FMEAs fit well within the Agile development environment as they are best when they evolve as development evolves.
This overview provides for a simple example of a software FMEA.
If you have enough data, you can predict anything. Even software failures can be predicted. How many software defects there are in a program is very predictable if you know how big it is, the practices and tools used to develop it, the domain experience of the software engineers developing it, the process and the inherent risks. There are certain development factors that indicate a successful software release. There are also certain factors that indicate a distressed software release.
Contrary to popular myth, a good development process is necessary but not sufficient. The best processes will not compensate for people who don't have industry experience or specifications that aren't written well or not enough people testing the software.
The facts show that processes are what separate the distressed from the mediocre. However, in our 30 years of data, processes did not distinguish between the successful and the mediocre. In other words, process keeps the program from complete failure but it won't guarantee sucess. Many other things have to be in place for that.
Our data shows that the short engineering cycles, frequent releases and "aiming small and missing small" is one of the most important factors.
Our data also shows that having people who understand the product and industry is more important than having people who know every insignificant nuance of a programming language.
Our data also shows that the reliability hinges on the quality of the specifications and design as opposed to how many pages are in the specifications.
Not only can the total volume of defects be accurately predicted, but when the defects will become manifested into failures can also be predicted.
It's been known for decades that what goes up eventually comes back down. When you add new features - the defects go up. When you test and remove them they go down. There is absolutely no rocket science involved with defect trending.
The types of defects are also very predictable as they directly link to the weakest part of development. For example - if you have a system that is stateful and you don't sufficiently design the state management - guess what? You will have a lot of state related defects. Similarly if you have a system with timing constraints and you don't sufficiently analyze the timing - guess what? You will have timing related defects.
The percentage of failures in a system that are due to software versus hardware is also very predictable. There is a simple rule of thumb. The amount of software continues to grow exponentially every year while hardware is slowly being replaced by software. So, if you know that last year your product had 60% hardware failures and 40% software failures that means that this year it will be no less than 40% and probably 10-12% more than that.
This page covers very simple methods for predicting the software failures before the code is even written.
An easy-to-use, automatic, self-contained toolkit to accelerate ODM* benchmarking NFVi-ready server designs on Intel® Scalable Server platforms based on golden benchmark to characterize baseline performance test on DPDK, QAT and OVS, running on a single Xeon SP server.
Top Ten things that have been proven to effect software reliabilityAnn Marie Neufelder
There are many myths about what causes reliable or unreliable software. However, this presentation shows the facts based on real data from real projects.
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
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!
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, 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.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
1. Version 1.0
EARS: The Easy Approach to
Requirements Syntax
John Terzakis
Intel Corporation
john.terzakis@intel.com
November 12, 2014
Better Software Conference
Orlando, FL