Any (functioning) system is built upon an infrastructure. This infrastructure supports all of the functions and activities of the system. Testing is no exception. With a good test infrastructure, QA teams can speed up their testing efforts and drastically improve efficiency. In this article, we will explore the concept of test infrastructure, and how you can effectively build one.

At the end of every testing project, a test report is usually created to summarize the results. This report provides insights into how the test project was executed if it aligned with the initial plan, and what areas need further optimization. In this article, we’ll explore in-depth what needs to be included in a test report, as well as the key metrics that QA teams need to look at if they want to gauge their testing efficiency.

For a software engineer, even the basic use of a debugger can save a lot of pain: adding breakpoints (places in the code the program will stop at and expose the current context) is very easy, and navigating from one breakpoint to another isn't difficult either. And with just that, you can say goodbye to a program's many puts and runs. Just add one or more breakpoints and run your program.

Kernighan & Pike, The Practice of Programming, 1999 Despite constantly changing technologies and the needs of customers, some wisdom seems eternal. Programmers need to test their code. But thorough testing takes time. When we do it well, everything works, and a massive testing effort feels like a waste. However, when we do it badly, our code is often broken, and we wish that we had done better testing. I have some good news for you.

Using BigQuery object tables, we analyze unstructured Cloud Storage data with generative AI models and join the results with BigQuery structured data.

Network Telemetry, in simple terms, is like having a conversation with machines or systems located far away. It’s about collecting data from these distant sources to better understand how they’re performing. Think of it as a health check-up, but for machines or systems instead of people. This technology plays a crucial role in a variety of fields.

Welcome to the latest entry in Yellowfin Japan’s ‘How to?’ blog series! In our previous blog, we created a pie chart that aggregates on the basis of category. By using set analysis, we were able to represent the percentage of Books Only in the numeric display, based on the composition of the items ordered.

This blog post is designed as a guide to illuminate the critical importance of software testing plans—a cornerstone in ensuring the delivery of reliable and high-quality software products as we described in a previous post when we described the process of creating a complete Test Plan. For QA professionals and testers, as well as for those developers that are getting initiated on a journey into the world of testing, this post serves as a reaffirmation of our principles.