This document discusses evaluating and testing web APIs. It covers several topics:
- The importance of API quality for customers who rely on APIs for their applications and business needs. High-quality APIs must be available, consistent, transparent, secure, performant, reliable and usable.
- Different approaches to testing APIs, including functional automation testing at different stages of the development process from continuous integration to production monitoring.
- Key aspects of API quality that should be tested, such as expected results and behaviors, error handling, internationalization, security, performance, and usability.
- The presentation aims to convey that thorough evaluation and testing of APIs is necessary to ensure they meet customers' needs and expectations.
API Testing: Answers to Your Top 3 QuestionsQASource
Want more? Visit our official blog, QALounge.com! Brought to you by QASource.com.
Pursuing API testing or API test automation for your product? Our engineers have answers to the top 3 questions about API automation testing in this slide deck.
API Testing: The heart of functional testing" with Bj RollisonTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-81-api-testing-the-heart-of-functional-testing
An API, or Application Programming Interface, is a collection of functions that provide much of the functional capabilities in complex software systems. Most customers are accustomed to interacting with a graphical user interface on the computer. But, many customers do not realize the much of the functionality of a program comes from APIs in the operating system or program's dynamic-link libraries (DLL). So, if the business logic or core functionality is exposed via an API call then and if we want to find functional bugs sooner than API testing may be an approach that provides additional value in your overall test strategy. Additionally, API testing can start even before the user interface is complete so functional capabilities can be tested while designers are hashing out the "look and feel." API testing will not replace testing through the user interface, but it can augment your test strategy and provide a solid foundation of automated tests that increase your confidence in the functional quality of your product.
An Introduction To Automated API TestingSauce Labs
As more and more apps are being assembled from a rapidly expanding array of microservices, APIs are the key to accessing these new architectures. That new feature you’re working on will often rely on upstream services that can only be accessed via APIs - so to test the functionality of the new component you’ll need to simulate those services.
While APIs are the backbone of the websites and apps we rely on today, automated testing of them is only starting to grow. Join Patrick Poulin, CEO of API Fortress, as he provides an introduction to API testing, the best ways to test your own APIs using popular tools available today, and demonstrates the orchestration of API tests and Sauce Labs tests as part of a Jenkins build process.
Key takeaways:
-Clearly understand what API testing means.
-Learn about best practices.
-See demonstrations of popular testing tools.
-See API and UI/UX testing implemented as part of a Jenkins build.
API Testing: Answers to Your Top 3 QuestionsQASource
Want more? Visit our official blog, QALounge.com! Brought to you by QASource.com.
Pursuing API testing or API test automation for your product? Our engineers have answers to the top 3 questions about API automation testing in this slide deck.
API Testing: The heart of functional testing" with Bj RollisonTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-81-api-testing-the-heart-of-functional-testing
An API, or Application Programming Interface, is a collection of functions that provide much of the functional capabilities in complex software systems. Most customers are accustomed to interacting with a graphical user interface on the computer. But, many customers do not realize the much of the functionality of a program comes from APIs in the operating system or program's dynamic-link libraries (DLL). So, if the business logic or core functionality is exposed via an API call then and if we want to find functional bugs sooner than API testing may be an approach that provides additional value in your overall test strategy. Additionally, API testing can start even before the user interface is complete so functional capabilities can be tested while designers are hashing out the "look and feel." API testing will not replace testing through the user interface, but it can augment your test strategy and provide a solid foundation of automated tests that increase your confidence in the functional quality of your product.
An Introduction To Automated API TestingSauce Labs
As more and more apps are being assembled from a rapidly expanding array of microservices, APIs are the key to accessing these new architectures. That new feature you’re working on will often rely on upstream services that can only be accessed via APIs - so to test the functionality of the new component you’ll need to simulate those services.
While APIs are the backbone of the websites and apps we rely on today, automated testing of them is only starting to grow. Join Patrick Poulin, CEO of API Fortress, as he provides an introduction to API testing, the best ways to test your own APIs using popular tools available today, and demonstrates the orchestration of API tests and Sauce Labs tests as part of a Jenkins build process.
Key takeaways:
-Clearly understand what API testing means.
-Learn about best practices.
-See demonstrations of popular testing tools.
-See API and UI/UX testing implemented as part of a Jenkins build.
Want to know what a leading software testing consultant perform API testing and API Implementation with steps to do it. As API testing focuses more on the testing of data responses, security and performance restrictions its implementation is a must so read thoroughly this blog, to take everything about API testing.
Talk given at Typeform for the Barcelona Bug busters meetup.
How to Automate API Testing guides you through a possible API Testing workflow for API Functional Testing exploring different tools and approaches.
What's even better than mocking? API Virtualization. This presentation will show you how.
With API Virtualization, quickly and easily create mocks to validate the APIs you depend on, then pump them up with some serious juice for more powerful application testing. In your own API sandbox, simulate API failure conditions to make sure your application can gracefully handle error responses.
Data Driven API Testing: Best Practices for Real-World Testing ScenariosSmartBear
Exceptional API delivery requires extensive testing – You test for function and performance. You test SOAP and REST. You test all of the things. But inevitably, real-world scenarios will vastly outnumber those designed in your automated testing process. How can you ensure that your testing covers the scenarios your API will encounter in the wild?
There might be two different scenarios while API testing. One when you are consuming API from other providers and the other one when you are designing API for your own application.
When you are developing API for your application, you should start for white box testing. The basic approaches are : unit testing, integration testing, edge test cases and security testing.
As an organization grows, the body of code that needs to be regression tested constantly increases. However, to maintain high velocity and deliver new features, teams need to minimize the amount of manual regression testing. Eric Smith shares his lessons learned in automating RESTful API tests using JMeter, RSpec, and Spock. Gain insights into the pros and cons of each tool, take back practical knowledge about the tools available, and explore reasons why your shop should require RESTful automation as part of its acceptance test criteria. Many decisions must be made to automate API tests: choosing the platform; how to integrate with the current build and deploy process; and how to integrate with reporting tools to keep key stakeholders informed. Although the initial transition caused his teams to bend their traditional roles, Eric says that ultimately the team became more cross-functionally aligned and developed a greater sense of ownership for delivering a quality product.
Introduction to APIs & how to automate APIs testing with selenium web driver?BugRaptors
BugRaptors expertise in using selenium IDE, Selenium WebDriver. For web and mobile applications we work with selenium webdriver by using different frameworks. We extensively use selenium IDE and web driver to automate all types of projects from small to large complex projects.
10x Test Coverage, Less Drama: Shift Left Functional & Performance TestingSauce Labs
Can you move faster, ship more often and still achieve greater test coverage than you do today? Yes! Learn how shifting left (building tests where and when code is built) and making those tests more focused in scope (atomic) and independent of each other (autonomous) can give you back your nights and weekends while increasing test coverage 10x or 100x. Once your tests are atomic and autonomous, you can run them in parallel and reduce time to feedback from hours or days to minutes.
In this webinar, technical experts from Sauce Labs and BlazeMeter share the essentials to building tests that scale in coverage without the brittleness of traditional automation approaches.
API Testing with Open Source Code and CucumberSmartBear
Ole Lensmar discusses various ways and tools for testing web APIs, focusing on using Cucumber. Watch the full presentation: https://www.infoq.com/presentations/api-testing-cucumber
Free and Open Source web service testing application.
Released in Sept. 2005, Developed by eviware software.
Built entirely on java platform & uses swing for UI.
Soap UI Pro is the commercial enterprise version.
Latest version 4.5.1
Introduction to using SpecFlow tool for testing REST API. For beginners that are at least a bit familiar with test automation, and gives some details and hints.
How BDD with tools like Cucumber can create a stronger team, a better quality product, and ultimately a more useable API. Given at the #apistrat SF conference 10/24/2013
Want to know what a leading software testing consultant perform API testing and API Implementation with steps to do it. As API testing focuses more on the testing of data responses, security and performance restrictions its implementation is a must so read thoroughly this blog, to take everything about API testing.
Talk given at Typeform for the Barcelona Bug busters meetup.
How to Automate API Testing guides you through a possible API Testing workflow for API Functional Testing exploring different tools and approaches.
What's even better than mocking? API Virtualization. This presentation will show you how.
With API Virtualization, quickly and easily create mocks to validate the APIs you depend on, then pump them up with some serious juice for more powerful application testing. In your own API sandbox, simulate API failure conditions to make sure your application can gracefully handle error responses.
Data Driven API Testing: Best Practices for Real-World Testing ScenariosSmartBear
Exceptional API delivery requires extensive testing – You test for function and performance. You test SOAP and REST. You test all of the things. But inevitably, real-world scenarios will vastly outnumber those designed in your automated testing process. How can you ensure that your testing covers the scenarios your API will encounter in the wild?
There might be two different scenarios while API testing. One when you are consuming API from other providers and the other one when you are designing API for your own application.
When you are developing API for your application, you should start for white box testing. The basic approaches are : unit testing, integration testing, edge test cases and security testing.
As an organization grows, the body of code that needs to be regression tested constantly increases. However, to maintain high velocity and deliver new features, teams need to minimize the amount of manual regression testing. Eric Smith shares his lessons learned in automating RESTful API tests using JMeter, RSpec, and Spock. Gain insights into the pros and cons of each tool, take back practical knowledge about the tools available, and explore reasons why your shop should require RESTful automation as part of its acceptance test criteria. Many decisions must be made to automate API tests: choosing the platform; how to integrate with the current build and deploy process; and how to integrate with reporting tools to keep key stakeholders informed. Although the initial transition caused his teams to bend their traditional roles, Eric says that ultimately the team became more cross-functionally aligned and developed a greater sense of ownership for delivering a quality product.
Introduction to APIs & how to automate APIs testing with selenium web driver?BugRaptors
BugRaptors expertise in using selenium IDE, Selenium WebDriver. For web and mobile applications we work with selenium webdriver by using different frameworks. We extensively use selenium IDE and web driver to automate all types of projects from small to large complex projects.
10x Test Coverage, Less Drama: Shift Left Functional & Performance TestingSauce Labs
Can you move faster, ship more often and still achieve greater test coverage than you do today? Yes! Learn how shifting left (building tests where and when code is built) and making those tests more focused in scope (atomic) and independent of each other (autonomous) can give you back your nights and weekends while increasing test coverage 10x or 100x. Once your tests are atomic and autonomous, you can run them in parallel and reduce time to feedback from hours or days to minutes.
In this webinar, technical experts from Sauce Labs and BlazeMeter share the essentials to building tests that scale in coverage without the brittleness of traditional automation approaches.
API Testing with Open Source Code and CucumberSmartBear
Ole Lensmar discusses various ways and tools for testing web APIs, focusing on using Cucumber. Watch the full presentation: https://www.infoq.com/presentations/api-testing-cucumber
Free and Open Source web service testing application.
Released in Sept. 2005, Developed by eviware software.
Built entirely on java platform & uses swing for UI.
Soap UI Pro is the commercial enterprise version.
Latest version 4.5.1
Introduction to using SpecFlow tool for testing REST API. For beginners that are at least a bit familiar with test automation, and gives some details and hints.
How BDD with tools like Cucumber can create a stronger team, a better quality product, and ultimately a more useable API. Given at the #apistrat SF conference 10/24/2013
How to Evaluate an API Without Writing a Line of Codeduvander
We all know there are thousands of APIs we could use, so how do you decide whether to take the time to integrate with one? API veteran Adam DuVander takes you through the areas you should consider, questions you should ask, and some tests you could run. All before writing a single line of code for your application.
Making the build self-testing is one of the best pratices of continuous integration. This was the main goal of this presentation, the work done in a REST API, using Symfony, phpspec, PHPUnit and Behat.
Rethinking Test Automation: The Case for Moving Beyond the User InterfaceCognizant
Rapid development models are forcing quality teams to balance speed with coverage. To enable both effective and efficient testing in this environment, businesses need to replace conventional UI-based automation techniques with more holistic approaches.
As predicted by Gartner, the demands for API testing and virtualization services are expected to rise exponentially because of the increasing intricacies in business logics and quickly changing IT environments. Independent software testing companies take a clue and explore this avenue.
Read More at: http://softwaretestingsolution.com/blog/api-testing-keeping-check-agile-software-development/
Presentation in Spanish given at DeSymfony Day 2014 in Barcelona about different approaches of testing with my teammate Jordi Llonch.
We created a GitHub repository comparing the main libraries available in PHP: https://github.com/Akamon/to-mock-or-not-to-mock
Nowadays, it is quite common to have build infrastructure that, on every change in a repository, builds your software and runs all your tests. However this is where most development teams stop. This talk demonstrates how you can consistently deploy systems from development to testing, staging and production.
With Bndtools we semantically version bundles in the Eclipse IDE. The continuous build is setup to automatically deploy to a bundle repository and create snapshots of changed bundles compared to a baselined version that is available in a release repository. By hooking up these repositories to Apache ACE, such updates can instantly be deployed to systems in different configurations, allowing you to deploy new features to QA systems, beta users and finally roll them out to all other customers.
This presentation was given at ApacheCon NA 2014, Denver.
his PDF provides valuable insights into API performance testing practices, emphasizing the crucial role they play in enhancing user experience, ensuring business success, and maintaining security. Learn about top practices, statistics, and expert guidance to harness the full potential of your APIs.
API testing is a critical component of the software testing process. Programmers, developers, and software analysts who collaborate to create a stable software product use a variety of tools to ensure the product’s quality.
In such a case, getting API testing right is one of the most important factors in determining whether a software item will be a success or a failure. From this list of recently reviewed web API testing tools, one can compare the tools to choose the best and get the best ROI by selecting an ideal tool for API testing.
The presentation on Test the REST was done during #ATAGTR2017, one of the largest global testing conference. All copyright belongs to the author.
Author and presenter : Varun Deshpande
API testing has established a trend for automated testing as software development teams become more technologically oriented. More tools will be developed to meet these requirements. Regardless of how difficult it is to find a tool that can do everything, adopting a toolset that meets a company’s needs while increasing revenue is critical. Before choosing one, consider how each API testing tool may be better suited for specific purposes and what features are essential for your software development workflows.
[WSO2 API Day Chicago 2019] Sustainable Competitive Advantage WSO2
Sustainable competitive advantage, while once a necessary part of any strategy, is now increasingly obsolete for most firms. The new path to winning means capturing opportunities quickly and exploiting them decisively. It's all about learning to thrive in a transient advantage economy. Transient advantage is the central thesis of Rita McGrath's recent book on competitive advantage. These principles are especially relevant for agile companies that pursue digital-first business models. Quinnox has adopted this philosophy for its clients and its own business where we believe enterprise integration driven by API's is the bridge to digital transformation, speed to market, and frequency to market.
API Testing Useful Tools Postman Tutorial And Hints.pdfiDataScientists
API web developers checking out beneficial app development equipment, Postman API web designers testing app developers tutorial. And, the tips API checking out enables observe software company logic. It’s part of integration checking, and no great guarantee app development technique is whole without it. However, guide API web designers checking out is quite a tiresome web development technique. So, QA Engineers app developers frequently select to automate it every time appropriate. Now, APIs web developers are numerous checking-out automation equipment and app development strategies available. However, The API web designers likes to walk you through some of our maximum favorite ones that will help you web development store time and obtain higher app development results.
Ole Lensmar, co-creator of soapUI and Chief Architect at SmartBear Software, gave this presentation at STARWEST 2012. We are working, he says, in the "Golden Age of APIs."
Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...Kin Lane
Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub).
Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas:
- Versions
- Monitors
- Mocks
- Environment
- Documentation
- Feedback Loops
The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s
apidays LIVE Hong Kong - Orchestrating APIs at Scale by Hieu Nguyen Nhuapidays
apidays LIVE Hong Kong - The Open API Economy: Finance-as-a-Service & API Ecosystems
Orchestrating APIs at Scale
Hieu Nguyen Nhu , Senior Cloud Native Technical Specialist at Microsoft
What’s behind a high quality web API? Ensure your APIs are more than just a ...Kim Clark
Web APIs have now become as important as websites for some enterprises. Dreaming up an attractive set of data resources to expose to your consumers is a critical step, but it's just the beginning. In the world of APIs, standards are rare, so common conventions are everything. Which should you choose, and how do you apply them to your data model? What architecture will ensure your APIs are robust, scalable, and secure? How do you ensure data integrity in an environment without transactionality? How will you prepare for huge changes in scale? How do you join your API world with your existing enterprise integration and SOA? Attendees will learn design practices to ensure their APIs are both attractive and consumable.
Webinar - Creating an app ecosystem for your APIs
As the API Economy grows, every Enterprise is asking itself – how do we leverage our APIs to extend the reach of our business? What do we need to go from having an API to creating a viable app ecosystem around our APIs? We will explore how Enterprises can create both internal as well as external ecosystems around their APIs. We will look into the lifecycle of Create, Publish, Manage, Consume, Monitor and Monetize on your APIs.
API testing is a type of software testing that involves testing application programming interfaces (APIs) directly and as part of integration testing to determine if they meet expectations for functionality, reliability, performance, and security.
PayPal operates in 200+ countries. The complexity of region specific requirements and a disjointed offering led to a situation where PayPal Checkout API product suite got polluted with many overlapping capabilities and an API documentation that was hard to comprehend, incomplete and inconsistent making the integration experience much harder than it needed to be.
There was a strong desire to act upon the feedback that we have been hearing from our merchants and developer community to make a turn for the better.
This talk aims to explore
> When is the right time for organization to rethink their API and launch a new version.
> Considerations that go into creating a new version of an API that is so central to the way thousands of developers and merchants integrate with PayPal.
> Explore challenges in design, adoption, migration both internally and externally within the organization.
APIs are the central hub of data for many applications which makes it very important to test the APIs for functionality, reliability, performance and security. Bugraptors offers the API testing services which save resources and efforts of manual regression testing.
To know more about API testing, visit www.bugraptors.com or email us at info@bugraptors.com
Spec-first API Design for Speed and SafetyAtlassian
Spec-first API design dramatically tightens and improves the development feedback loop without wasting effort on artifacts that can't be used.
The Jira Software team has used this approach very successfully to build APIs that we expose to both internal and external consumers.
In this session, James Navin will walk you through the spec-first approach and demonstrate the benefits that it brings. He will also highlight some tools that can be used to implement a spec-first development approach.
With special guests Ron Ratovsky and Darrel Miller from the OpenAPI Initiative's Technical Steering Committee, this SmartBear webinar session covered the history of Swagger and the OpenAPI Specification, and all the latest changes in OAS 3.1.
IATA Open Air: How API Standardization Enables Innovation in the Airline Indu...SmartBear
The necessity of surviving during the economic upheaval of a global pandemic is fueling innovation in the airline industry. A new age of aviation is being built on digital technology and APIs to improve data sharing, reduce costs, and optimize revenue for carriers.
API standards are the key to the success of any digital initiative, enabling interoperability between independent parties. The International Air Transport Association (IATA), the industry trade association responsible for developing the global standards for airlines, are utilizing SwaggerHub, the API design and documentation platform, to help bring these best practices to life.
In this webinar session, we explore:
How IATA’s Open Air initiative allows the industry to open up its digital capabilities for innovation
Open Air standard as the common technical approach to describing API definitions
Best practices for scaling API design and standardization across the industry
A live API design demonstration with SwaggerHub and IATA
The State of API 2020 Webinar – Exploring Trends, Tools & Takeaways to Drive ...SmartBear
Since 2016, SmartBear has been surveying the State of APIs to better understand the trends and technologies associated with this essential digital building block. We have just completed the State of API 2020 survey and will be sharing the research findings during this live webinar.
We will be sharing research from over 2,000 respondents on how organizations are bringing APIs to market in 2020, what tools they are using, how they view certain trends, and where they see the market going.
How LISI Automotive Accelerated Application Delivery with SwaggerHubSmartBear
In this SmartBear webinar, Sebastien Gadot presents on how his team at LISI Automotive got started with the open source Swagger tools and moved to SwaggerHub to speed up their application delivery.
Standardising APIs: Powering the Platform Economy in Financial ServicesSmartBear
In this webinar session, SmartBear and SWIFT discuss the importance of API standardisation and the role it plays in the new platform economy in the financial services industry.
Adopting a Design-First Approach to API Development with SwaggerHubSmartBear
In this webinar session, we discussed why many software development teams are looking at taking a design-first approach to their API development. We highlight benefits like early collaboration and treating APIs as products.
Standardizing APIs Across Your Organization with Swagger and OAS | A SmartBea...SmartBear
In this webinar session, we showed why API standardization is important and how your organization can use SwaggerHub to overcome the most common challenges with making the move to the OpenAPI Specification.
As APIs continue to become a core focus of organizations, ensuring quality is a major factor at every stage, while also speeding up development. To embrace this reality, we must develop pragmatic approaches for closed-loop processes, outcome-oriented development, and effective change management techniques to deliver on the promise of APIs. Joe Joyce, Solution Engineer at SmartBear will discuss these modern issues and outline impactful approaches for you to resolve the daily challenges they present.
Artificial intelligence for faster and smarter software testing - Galway Mee...SmartBear
How Artificial Intelligence (AI) is changing software quality
Hybrid test automation framework to test identified and unidentified UI properties
Demonstration of a use case with AI in UI test automation for any skill level
The Best Kept Secrets of Code Review | SmartBear WebinarSmartBear
In this webinar session, we share a comprehensive list of peer code review best practices, distilled down years of SmartBear research and case studies. At the end, we shared how our code and document review tool, Collaborator, can help teams put these tactics into practice.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
25. Bad Error Messages…
Change unexpectedly
Don’t match their status code (HTTP)
Don’t tell users what they did wrong
Don’t tell users what they need to do right
Show clients stuff that could be misused
26. APIs are global from day 1
Dates & Timezones
Regional Formatting
Localized Messages / Errors
29. TestCase API 1 API 2
Request 1
Response
validate
API Functional Test Automation
30. TestCase API 1 API 2
Request 1
Response
Transfer parameters
Request 2
Response
validate
validate
API Functional Test Automation
31. TestCase API 1 API 2
Request 1
Response
Request 3
Response
Transfer parameters
Request 2
Response
Transfer parameters
validate
validate
validate
API Functional Test Automation
33. Pre vs Post-Deployment Quality
Continuous
Integration
(Agile)
Continuous
Deployment
(DevOps)
Automated
Test Execution
months/weeks/d
ays/hours
34. Pre vs Post-Deployment Quality
Continuous
Integration
(Agile)
Continuous
Deployment
(DevOps)
Automated
Test Execution
Production
Monitoring
months/weeks/d
ays/hours
Test asset re-use
By the end of this session you will have turned into juvenileexperts on the key components of API Quality. In your organization, whenever you hear about API initiatives and how you should test them– you will be able to raise your hand and say “I know all about that – a chap at StarWEST with a funny accent – he spelled it all out for us” – and you will be able to rise and help your company or team produce the finest APIs yet to be seen. If not – I have failed – and you can let me know on the evaluation talon. Or you can mailme to tell of your endeavors – I want to know!But - to get us there in mere 40 minutes I will be in a constant hurry – nevertheless - please don’t hesitate to interrupt if you have any questions – after all – my fate as an API aficionado lies in your hands.
First – do we all know what I mean by Web APIs? Do we have a common understanding? Because many of you might be thinking; what’s the big deal? An API is an interface for a system – testing them is no different than testing other code; we test that they “work”, we report bugs, we hug developers because they involve you early in the process, we make sure performance is ok - and we put them into production – how hard can it be? Well –that’s not the whole story – but to make my case I need to give you some context on the evolution of Web APIs – where they come from.
One way to look at Web APIs is from a technology point of view – SOAP/XML -> REST/JSON -> Asycn (WebSockets, etc)And trust me when I say that I could talk a lot about these technologies - But that’s not really it – that’s not where the real action is when it comes to the fuss around APIs – to understand what the noise is all about we need to take a step back
20 years ago (monolithic) -> 10 years ago (SOA) -> now (WOA)
20 years ago (monolithic) -> 10 years ago (SOA) -> now (WOA)
Suddenly – APIs are at the heart of a companies business – having evolved from being strictly internal where they used to be building block with a controlled environment, usage, dependencies and lifecycle are totally within the owning business – they now are the business, and as such have a totally different context; their usage is unpredictable – their lifecycle is controlled by others – they are subject to competition from other API providers – and their users are biased from day one on how an API should be. That’s a totally different challenge for QA than an API that is strictly internal – in a controlled environment. Of course – the functional and performance aspects still apply – but suddenly a bunch of other traits related to QoS and Usability are of primary concern for the API (and thus your business) to succeed.
So, let’s try to drill into this a little bit… who are the actual stakeholders for API quality? Who really needs it – and what is important to them?
Bruno Pedro at apiux.com created this API Hierarchy of Needs – trying to visualize the needs of an API for it to be successful. What’s really interesting to note here – and something the spurred some debate – is that usability is at the bottom of the pyramid. He argues that it doesn’t matter how well an API works or how reliable it is – if you can’t use it, it doesn’t matter.
Keeping the API Hierarchy of needs in mind, lets start with the insight that although APIs are ultimately invoked by code – they are initially always consumed by people - Developers, Testers, the like! And for you to be able to do that in an efficient and satisfying way – the API has to be usable – which brings us to the perhaps most important prerequisite for a successful API : it’s usability – how easy is it to use the API?
Know your users – is it Josh, the HTML5 Hscker? Is it John the j2EE Expert?
You might have heard of the term UX before – User Experience, and similarly the term DX (Developer Experience) designates how easy it is for a Developer to consume and API – and this is where API Usability experts have to focus; on the developers that will initially be tasked with integrating the API. We all know that developers are a special bunch – and as such have special needs – lets explore some of them.
Know your
So let’s say we are going to use an API – how do we get started?
Metadata is a somewhat heated subject in some API communities; with SOAP there has never been an issue – but with REST (which was a countermovement to SOAP in a certain sense) – there has been a lively debate. The main argument against metadata has been that it is hard to maintain – which isn’t always true. The advantages for metadata are on the other hand several:Code generationAutomated validationDetailed understanding of complex messagesFor testers: possibility to measure coverageWhat can metadata give that documentation doesn’t? Isn’t metadata a kind of documentation?
The APIs you create are most often consumed in some kind of context – and if that context is well established it usually already follows certain rules/heuristics applicable to the task at hand. For example, let’s say your API is related to geospatial information – and that your users often also use the Google Maps APIS
This is a test that attempts to measure API Usability: the 3:30:3 Test. Devised by OriPekelman – it might not be the most scientifically correct – but it does give an indication of what is important. When visting a companies API developer portal, it should take: 3 minutes to understand what the API does, 30 seconds to sign up, and 3 minutes to be able to make your first call to the API.
Finally – and this is perhaps the one many layman testers think of first (not you of course) – the direct stakeholder of the API is the code that integrates with it – because ultimately, in production, APIs are invoked by code – not people. This is where functional testing, test automation, automated test execution all come into play. Let’s look at some hands on examples.
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
Here you test for expected and unexpected results. Test not only the content of the results – but also the format. Going back to the discussion on usability and nomenclature – make sure that if you use a common nomenclature (for example for coordinates) use the right data-types as well. Make sure you do both positive and negative tests – error messages are equally important.Formatting, DatatypesValuesConsistency
This error message for example – can anyone see what’s wrong with this?
One thing that I haven’t really emphasized is that APIs are global from day 1 – their consumers could be calling in from all over the world – and if your API makes use of dates, times and timezones that is a common area for problems. Make sure that the system handles this input correctly.
You chain multiple requests together to test entire transactions – transferring content in a response to the following requests.
You chain multiple requests together to test entire transactions – transferring content in a response to the following requests.
You chain multiple requests together to test entire transactions – transferring content in a response to the following requests.
You chain multiple requests together to test entire transactions – transferring content in a response to the following requests.
If you’re in an agile shop doing continuous integration you might want to set up corresponding continuous testing processes – and if you are doing automated deployment – you should perhaps consider to reuse some of those pre-deployment testing assets as post-deployment functional monitors.Exploratory Testing!
If you’re in an agile shop doing continuous integration you might want to set up corresponding continuous testing processes – and if you are doing automated deployment – you should perhaps consider to reuse some of those pre-deployment testing assets as post-deployment functional monitors.Exploratory Testing!
If you’re in an agile shop doing continuous integration you might want to set up corresponding continuous testing processes – and if you are doing automated deployment – you should perhaps consider to reuse some of those pre-deployment testing assets as post-deployment functional monitors.Exploratory Testing!
Finally - consider this: since and API is consumed by a machine there is no “wiggle-room” as there is for the previous two stakeholders – which could be expected to adapt to lack of quality in certain areas. Here it’s straight forward: either it works, and delivers the desired functionality – or it doesn’t and the customer gets strange error messages.
The next Stakeholder is the business that is using your API. Think about it: their business (and perhaps entire existence!) depends on it – if your API doesn’t work as they need it to – both their reputation (and yours!) is at great risk! For them a different number of aspects come into play – all wrapped up in the somewhat boring term “Quality of Service”.Now – QoS isn’t new to Web APIs – it is equally important for internal APIs - but the big difference is that for Web APIs you can’t really foresee how and in which context your API will be consumed – which makes it even more important that you are one step ahead in regard to your APIs quality. I’ll give you three main areas:
Reliability – can they rely on your service being available? Will you provide consistent response times? For a mobile app – do you give consistent results from all over the world? -> You can highlight these and make sure that Monitoring – from all over the world.
Security – this is a biggie – we’ve all heard about security breaches at facebook, twitter, the Playstation Network. You customers want to know that any data they enter into your system that belongs to them – can never – and I mean never – come into wrong hands. -> Security Testing
Performance / Scalability – this is the really hard part: what if your API is a building block in the latest startup craze? What if load increases from 100s request per minute to 1000 requests/sec over the timespan of a couple of weeks – or days? Are you prepared? Should you be? Do you want to miss out on that opportunity? If you can scale successfully with your customers – they will be loyal and love you forever. Incidentally – you can see your own business as an equally invested stakeholder – the same requirements apply. And added dimension such as competitors enter the discussion -> is your API better than the competition in these regards?
OK – you’ve all been very brave and patient - lets recap this a bit: API Quality has three primary stakeholder and corresponding areas of concern:Users: User Experience -> required by the people initially consuming the APIBusiness: Quality of Service -> required by the business depending on the APICode: Consistent Functionality -> required by the code calling the API And although perhaps some of this is outside the scope of your role at your company – you can be that champion – you can be the one that brings these things to the attention of those building the API: I’m sure you remember that I made a promise - let’s revisit that and look at how I hope things to play out when you get back to your offices: