BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Automated testing Content on InfoQ

  • How to Remain Agile While Scaling

    Managing the complexity and scale of both the business and the software were key challenges as Yext started to grow, said Sean MacIsaac at Agile Business Day 2019. Yext addresses this by having product solutions that are broadly applicable and configurable by their customer team, and by hiding complexity with independently deployable services with clearly defined interfaces.

  • Google Enables Continuous Testing Using the Android Emulator

    The Android Emulator is the main tool Android developers use to test their apps. Google has just made integrating the Android Emulator within a continuous testing pipeline easier by open sourcing the Android Emulator Container Scripts and two related tools.

  • Introduction to Stateful Property Based Testing - Lambda Days 2019

    Tomasz Kowal, tech lead at ClubCollect, presented at Lambda Days 2019 an introduction to stateful property based testing. Property-based testing helped major companies find bugs which were not caught through example-based testing. Stateful property-based testing leverages an underlying model of the system under test to generate interesting test sequences, increasing the likelihood of finding bugs.

  • Optimize Automated Testing Using Defect Data

    By integrating the test framework and the bug tracking system, it becomes possible to deactivate test cases for known bugs and reactivate them when the bug is solved. Aneta Petkova, QA chapter lead at SumUp, presented The Framework That Knows Its Bugs at TestCon Moscow 2019.

  • Jest 24 Improves TypeScript Support, Plans Migration to TypeScript

    The Jest team recently released version 24 of their JavaScript testing framework which improves its support for TypeScript test authoring. The Jest team also announced plans to migrate their codebase from Flow to TypeScript in the near future.

  • How to Avoid Failing at Mobile Test Automation

    Test automation in mobile development should be done by the Scrum team; don’t set up separate test automation teams, said Nadya Denisenko. She advised obeying the testing pyramid for mobile testing and involve testers from the start. Testers are quality-oriented developers who can guide and assist other developers in delivering high-quality software; manual testing will disappear in the future.

  • Q&A with Katrina Clokie on Testing in DevOps for Engineers

    Wellington's DevOpsDays NZ recently closed with a keynote by Katrina Clokie on the Testing Skills and Superpower which engineers can utilise in a DevOps setting. The author of A Practical Guide to Testing in DevOps spoke with InfoQ to discuss the changes she's seen in the testing landscape and how this is further impacted by the move to embrace DevOps principles.

  • An Evolution of Chaos Experimentation: Kolton Andrus at ChaosConf 2018

    At the inaugural ChaosConf, held in San Francisco, USA, Kolton Andrus presented an evolution of chaos experimentation over the past eight years. He argued that the human and organisational aspects of dealing with failure should not be ignored, and also suggested that tooling should support application- and request-level targeting of failure injection tests in order to minimise the blast radius.

  • How Continuous Delivery Impacts Testing

    With continuous delivery we need to focus on quality as we write the code. Not every team will have testers, but if there are testers then they will work closely with developers, writing code to automate the small number of tests that cannot be covered by unit tests while helping developers creating unit tests.

  • Compliance in an Agile World

    Compliance is about making sure that you are doing the right thing and being able to prove it. With agile and frequent deliveries, you need to build compliance into the process of delivery. Making compliance obligation part of the thing that DevOps teams own increases the likelihood of success.

  • Netflix Announces Polly.JS HTTP Interaction Library

    Netflix recently announced the release of Polly.JS, an open source library for recording, replaying and stubbing HTTP interactions.

  • Learning to Bend But Not Break at Netflix: Haley Tucker Discusses Chaos Engineering at QCon NY

    At QCon New York, Haley Tucker presented “UNBREAKABLE: Learning to Bend But Not Break at Netflix” and discussed her experience with chaos engineering while working across a number of roles at Netflix. Key takeaways included: use functional sharding for fault isolation; continually tune RPC calls; run chaos experiments with small iterations; and apply the “principles of chaos”.

  • Microsoft Edge Now Supports W3C WebDriver Recommendation

    Microsoft Edge now supports the recently ratified W3C WebDriver recommendation, making it easier to automate unit and functional tests with Edge. WebDriver is also now an Edge Feature on Demand, providing automatic WebDriver updates for each release of Edge.

  • Chaos Engineering at LinkedIn: The “LinkedOut” Failure Injection Testing Framework

    The LinkedIn Engineering team has recently discussed their “LinkedOut” failure injection testing framework. Hypotheses about service resilience can be formulated and failure triggers injected via the LinkedIn LiX A/B testing framework or via data in a cookie that is passed through the call stack using the Invocation Context (IC) framework. Failure scenarios include errors, delays and timeouts.

  • Testing Software with Artificial Intelligence

    Advances in computer vision algorithms and the application of modern artificial intelligence (AI) techniques have made writing visual tests practical. With AI in testing, autonomous testing becomes possible. The boring and rote tasks will be delegated to the AI so that the tester can do the thinking.

BT