Experience leads to knowledge
Performance Testing for Game Development: Process Automation
Mobile games require performance testing before they hit the markets, otherwise a game built for a high-end device can get complained about by thousands of users and cause financial and reputational losses. Luckily, most key market players do realize it and run performance and load tests on a regular basis, during development, before every next release, etc., so the testing process becomes a necessary routine.
5 Most Common Mistakes to Avoid in Performance Testing Projects
A wise man once said, Only those who do nothing make no mistakes. That is why we devote this post to mistakes often made in load and performance testing projects. This post was written not only for managers who are up to their first testing project, but also for leading engineers who have had many of them and have many stories of their own to tell. The focus of this text is on performance testing, although there obviously may be many mistakes in any part of a complex IT project.
Automating Performance Testing Results: Best Practices. Part 3
In Part 1 of this tutorial, we had a close look on how to update your load testing environment to make load testing results automation possible. Instead of preparing your load testing report manually for days, with the environment discussed above, your data structure will depend on you, not you on your data structure. In Part 2, we’ve tackled a problem that engineers in every load testing company complain about, — namely, how Grafana slows down the system, — and several other quick fixes to your Grafana dashboards. We plunged into multiple databases and data sources, retention policies and tag filters. Finally, in this part we want to enable you to automate your test reports using all the infrastructure you have hopefully designed after reading through parts 1&2.
Project Management in Performance and Load Testing Projects
There are basically two models of providing performance testing services to the customer: outstaff and fixed price. If your customers chose outstaffing, it means they have an experienced testing engineer on staff. This person will be able to set goals and tasks for the testing process and act as a performance testing manager. In this case, they only pay your engineers’ hours, and take full responsibility for the results. Fixed price means that the responsibility is on your side. Your customer can’t run the tests themself, and wants a package deal. As a performance testing manager, you’re going to have to design everything from scratch. In this article, we’re looking at stages of a fixed price project, as seen by a QA project manager.
Be the first one to know
We’ll send you a monthly e-mail with all the useful insights that we will have found and analyzed
Testing Environment in the Project Lifecycle
To launch a product, you often need several testing environments. But why? Why pile up equipment, overload engineers with tasks, and hire more staff? Is it really inevitable? We will take a closer look at this problem below, but trust us, it is.
Automated vs Manual Mobile App Testing: Do You Need Both?
Software testing is a crucial part in creating a successful project. By assessing every facet of the product, a developer will know if the code meets business requirements. It’s through the testing that companies increase user tolerance and improve the performance of their apps. Having said that, testing is only as beneficial as it is efficient. There are two main approaches to testing – manual or automated. Both are critiqued and advocated all over the web, so choosing the one to fit your project is not an easy task. In this post, we’ll give you a brief rundown on the difference between them, their respective pros and cons, and the ways developers can take advantage of both.
Automating Performance Testing Results: Best Practices. Part 2
In this part, let’s tackle a problem that engineers in every load testing company complain about, — namely, how Grafana slows down the system, — and several other quick fixes to your Grafana dashboards.
Automating Performance Testing Results: Best Practices. Part 1
In this article, we start with a major topic, and then, in the following parts, we’ll go deeper into super-hardcore stuff. Test reports automation is the way to optimize testing costs and make performance testing more affordable. By cutting the cost, you will also be able to attract smaller businesses as customers. Good news: test reports automation is possible with the help of such popular tools as Grafana and InfluxDB, that all testers are already familiar with, to say the least.
People love to read
Explore the most popular articles we’ve written so far
- TOP 10 Best Online Load Testing Tools for 2024 Nov 7, 2024
- Top 11 Best Load Testing Tools 2024 Feb 14, 2024
- Top 10 Current Trends in Software Testing for 2024 Jan 15, 2024
- How to Increase Shopify Store Speed Mar 31, 2023
- 10 Ways to Optimize Cloud Costs Feb 20, 2023
- Importance of Software Testing in SDLC Feb 10, 2023
- 10 Steps to Great Mobile App Performance Testing Using JMeter Nov 30, 2022
- 10 Steps to SAP Performance Testing Mar 31, 2022