InfoQ Homepage Testing Content on InfoQ
-
Test Automation Requires a Strategy and Clean Code
Having a good strategy for test automation can make it easier to implement test automation and reduce test maintenance costs. The test automation pyramid and automation test wheel can be of help when formulating a test automation strategy and plan. Test automation code should be clean code, and treated similarly to production code.
-
How to Assess Software Quality
The quality practices assessment model (QPAM) can be used to classify a team’s exhibited behavior into four dimensions: Beginning, Unifying, Practicing, and Innovating. It explores social and technical quality aspects like feedback loops, culture, code quality and technical debt, and deployment pipeline.
-
Google Address Validation API Is Generally Available to Improve Address Accuracy
Google recently announced the general availability of the Address Validation API. The new feature of the Google Maps Platform validates an address, standardizes it for mailing, and determines the best-known geocode location for it.
-
Using Code Instrumentation for Fault Injection at the Application Level at eBay
eBay engineers have been using fault injections techniques to improve the reliability of the notification platform and explore its weaknesses. While fault injection is a common industry practice, eBay attempted a novel approach leveraging instrumentation to bring fault injection within the application level.
-
Helping Teams Deliver with a Quality Practices Assessment Model
The quality practices assessment model explores quality aspects that help teams to deliver in an agile way. The model covers both social and technical aspects of quality; it is used to assess the quality of the team’s processes and also touches on product quality. With an assessment, teams can look at where their practices lie within the quality aspects and decide on what they want to improve.
-
Testing Advanced Driver Assistance Systems
Advanced driver assistance systems can have a huge number of test cases. Cutting the elephant into smaller pieces can ensure every bit and piece is tested. A good test environment is essential to be efficient, fast and flexible to cover all required tests to ensure quality. Testers should be involved in the project right from the beginning to avoid task-forces, quality- or delivery problems.
-
Enhanced Serverless Development with Terraform and AWS SAM
AWS announced support for local development and testing of AWS Serverless Application Model (AWS SAM) apps defined in Hashicorp Terraform configuration files. The functionality is provided via the AWS SAM Command Line Interface (CLI) and is currently released as a public-preview.
-
JetBrains Previews Aqua, New Test Automation-Oriented IDE
JetBrains Aqua, now available in preview, is a new IDE focusing on test automation and integrating a number of distinct tools that are at the core of an automation engineer's daily routine, says JetBrains. Its features include multi-language support, an HTTP client and a Web inspector, database management, integrated Docker support, and more.
-
How We Can Use Data to Improve System Quality
To understand how systems are being used, we can collect metrics and identify trends over time. The data and insights gained can be used to improve system quality by improving software design or testing patterns.
-
Scalable Automation Frameworks for Functional and Non-Functional Testing
Separating the capabilities of a testing framework from the actual tests can enable scaling automated testing for complex enterprise products. According to Alexander Velinov, we should agree on the types of tests to execute automatically during release and what should be kept as manually triggered tests.
-
Komodor's Dashboard Brings Improved Debugging to Helm
Komodor's dashboard brings improved debugging to Helm. Helm Dashboard allows developers to quickly understand the status of Helm releases, with an intuitive interface showing the health of both the releases and the Kubernetes resources. The Dashboard provides visibility of common issues such as image version errors, resource limit problems and misconfiguration of secrets.
-
ArchUnit Verifies Architecture Rules for Java Applications
ArchUnit is an open source extensible library written in Java for verifying the architecture of Java applications. ArchUnit allows developers to enforce architecture rules such as naming conventions, class access to other classes, and the prevention of cycles. The library was originally created in 2017 by Peter Gafert and version 1.0.0 was released in October.
-
Performance Testing Should Focus on Trends
Performance testing starts by setting a baseline and defining the metrics to track together with the development team. Nikolay Avramov advises executing performance tests and comparing the results frequently during development to spot degrading performance as soon as possible.
-
Reliable Continuous Testing Requires Automation
Automation makes it possible to build a reliable continuous testing process that covers the functional and non-functional requirements of the software. Preferably this automation should be done from the beginning of product development to enable quick release and delivery of software and early feedback from the users.
-
JUnit 5.9 Supports GraalVM Native Image
JUnit 5.9 resolves various bugs and introduces a number of new features such as the ability to keep temporary files after executing a test. New annotations provide the ability to either enable or disable specific tests when running in a GraalVM Native Image. XML reports are now stored in the Open Testing Reporting format.