Performance Testing

Business

BrightScan

Test Automation

Security Testing

ERP Testing

Human Capital

Flex Testing

Technical Thursday

De Winter

Agile automated testing

Nowadays many companies are working Agile or are switching towards it. Agile allows you to deliver new features faster and more efficiently. But how can we assume the quality of those new features?&nbsp;<h2>What is agile (testing)?</h2>The Agile methodology is all about delivering incremental improvements to your product and can be achieved through processes like Scrum. It splits the development of the product into small sprints. At the beginning of each sprint, you need to prioritize the features you will be working on. At the end, you need to check if you have delivered what the user needs. The results are many small incremental product releases, which must be tested for quality and stability.In the past, when using a waterfall process, testing happened only once you had completed the entire development of the product. Nowadays, we see many specification changes during the development process. This also means that the QA team is faced with testing against a constantly shifting target. So, Agile requires testing to be done continuously throughout development.In other words, you’ll need your testing to be Agile as well. This implies that you should be able to test the whole product during every development sprint.&nbsp;In most cases, this will only be feasible by using test automation. The computer will interact with our UI and will replicate the actions of a real user. Typically, these types of tests will rely on tools like Selenium, Cypress, …&nbsp;<h2>Agile automation challenges</h2>The&nbsp;Agile methodology is the fastest approach to turn an idea into reality. Especially for dynamic projects that are constantly changing. The biggest advantage of working Agile is the capability of continuous iteration. But this is also the root cause of many major obstacles.<h3>Test creation</h3>Developing an automated test can take several hours or sometimes even days, especially when dealing with complex UI applications.&nbsp;That is because each test needs to be implemented, tested and debugged.&nbsp;Adding cross-browser and cross-platform support can make this process even slower.&nbsp;When testing new features during a sprint, the time needed for test creation might become a bottleneck.&nbsp;<h3>Regression testing</h3>Agile methodology’s nature is meant to adapt to continuous changes. For every single update, the application’s code-based and UI layers must be tested again to assure they are functioning correctly upon these new changes. This results in a massive amount of regression testing for QA teams to perform.&nbsp;<h3>Test debt</h3>During each sprint you only have a limited amount of time. That time needs to be split up between creating tests for the new features that are developed within this sprint, maintaining existing regression tests and executing and analyzing all the results.&nbsp;Thus, test maintenance for the regression tests will increase with each sprint and eventually the team won’t be able to complete all the work they need to do. This ever-increasing backlog of overdue test maintenance is what we call&nbsp;test debt.&nbsp;Agile testing requires your team to follow an Agile approach, breaking down their work based on sprints of the development team.&nbsp;During every sprint the test team needs to prioritize between automating new features, maintaining existing automated scripts&nbsp;and running tests manually. But test debt means that something has to give and the test team ends up making though decisions simply to meet the sprint goals.&nbsp;<h3>Maintaining</h3>Automated UI tests are very fragile.&nbsp;Since for many applications the elements are missing a unique id, we often need to rely on CSS or xPath selectors.&nbsp;Our automated test uses these selectors to identify the correct element to interact with.&nbsp;The downside of these types of selectors is that they can change unpredictably whenever the UI is updated during sprint.&nbsp;If such a selector changes, there are two possible outcomes: the test breaks because the selector is broken and cannot find an element or the selector selects the wrong element to interact with and the test fails several steps later.&nbsp;Each time the UI of your application changes, you also need to maintain your CSS and xPath selectors.

At Brightest we have developed our own Brightest automation framework. Which is designed as a future-proof solution and is independent of any vendor.

<h2>Are there any solutions?</h2><h3>System and service level</h3>In an Agile workflow the UI is bound to experience many changes.&nbsp;In terms of UI maintenance, test automation tends to be very time-consuming.&nbsp;To keep maintenance costs down and enhance the overall coverage, automation needs to be executed as much as possible on system and service level.&nbsp;Creating, executing and maintaining an automated API test takes much less time than an automated UI tests.&nbsp;That’s why we must try to keep the number of automated UI tests as low as possible.&nbsp;<h3>Unique ids</h3>When you create an automated UI test, make sure to use as much&nbsp;unique ids as possible. It will result in faster test creation, less failures and less maintenance when small UI changes are done to the application.&nbsp;<h3>Automation framework</h3>Use an&nbsp;automation framework.&nbsp;An automation framework is a combination of guidelines and structured code.&nbsp;When the framework is well-designed, it will have many benefits:<ul><li>A well-designed framework will encourage re-usability across your tests, which will result is less maintenance.</li><li>A keyword-driven framework will speed up the process of creating new tests for new features during the sprint.&nbsp;The keyword-driven framework in combination with the framework guidelines, will result in a readable and understandable way of writing a new test. And that even for less technical people.</li><li>Separating the framework from tests and test objects will result in less maintenance. Since any change in a test will have much less impact on the test objects and the framework itself.&nbsp;The same goes for any change in any of the test objects, this will have no impact on the tests and the framework itself.</li><li>A standardized way of working across all teams.</li></ul>A framework has many benefits in an agile environment, but it still needs to be developed. It will take time, but it will only be a one-time effort.&nbsp;Once implemented in the correct way, the same framework can be used for all projects without any extra effort.&nbsp;<h2>Brightest&nbsp;Automation&nbsp;Framework</h2>At Brightest we have developed our own Brightest&nbsp;Automation&nbsp;Framework, which is designed as a future-proof solution and is independent of any vendor.&nbsp;This framework is extendable and can be customized depending on your needs and requirements.&nbsp;No fairy tales, complex applications require complex automation. With this framework, we try to minimize the complexity for the tester who’s creating the tests. It’s made based upon all our previous experiences and will for sure kickstart your <a target="_blank" rel="noopener noreferrer" href="https://www.brightest.be/solutions/test-automation">test automation</a>!

Contact us

Interested in how test automation can help your organization?

Agile testing.jpg

Geeurickx

Why is security testing so important for the banking industry?

The financial sector is about 300 times more vulnerable to cyber-attacks than other sectors. Data breaches lead to a lack of trust among their customers. It is therefore important for the banking industry to put extra effort into their security testing. By conducting regular security checks, banks can identify and fix vulnerabilities before they are exploited.&nbsp;<h2>History of banking</h2>The first banks already go back to the time when the first currencies were minted, around 2000 BC. People needed a place to store their money whereas societies needed a functional system to facilitate trade and collect taxes. Banking started to play a crucial role in the economic stability of countries. Banks became the most important components for managing financial transactions of individuals and businesses.In the recent decades, the banking sector is experiencing a rapid change in ecosystem with the rise of digital technologies. Digital transformation aims to integrate computer technologies into an organization’s business processes and strategies. All of this to enhance customer experience and increase operational efficiency. The objective is to improve customer satisfaction, increase revenue, reduce costs and risks, and maintain a competitive edge in the market.&nbsp;<h2>Cybercrime in banking</h2>However, the growth of digital banking also implied more opportunities for cybercrime to happen. According to research, the financial sector is 300 times more vulnerable to cyber-attacks than any other. Hackers are always on the lookout for vulnerabilities. That is why security testing is vital for the banking industry to identify and resolve security issues.&nbsp;<h2>Security testing in banking</h2>The banking sector is highly regulated and must follow strict security standards. As such, several types of testing are crucial in ensuring security. Some examples of testing techniques include:<ul><li>Application security testing The process, practices, and tools used to identify, repair, and protect against vulnerabilities in applications (Web/API)</li><li>Network security testing Involves testing the security of a bank's network infrastructure, including firewalls, routers, and switches, to identify any potential weaknesses</li><li>Data security testing Used to verify the security of data at rest and in transit, including encryption and access controls</li><li>Penetration testing Simulating a real-world attack on the system to identify vulnerabilities and test the effectiveness of security controls</li></ul>At Brightest we strongly emphasize the importance of these types of security testing. They all have their specific approach, tools to use, expertise, etc. For this we also keep a close connection with the OWASP (Open Worldwide Application Security Project), an international organization dedicated to cyber security. OWASP lists the most critical security risks based on the extensive knowledge and experience of security experts around the world. Risks are ranked according to frequency, severity and impact.&nbsp;<h2>Phishing</h2>Next to this, there is also phishing to consider. <a target="_blank" rel="noopener noreferrer" href="https://www.brightest.be/blog/security-phishing">Phishing</a> is a type of online scam where a fraudulent message or mail is sent that appears to come from a legal institution. Its goal is retrieving sensitive information like login credentials, credit card numbers, etc. Around 91% of successful data breaches started with a phishing attack.With our partner <a target="_blank" rel="noopener noreferrer" href="https://www.knowbe4.com/">KnowBe4</a>, we build customized phishing simulations that are sent to company employees. Statistics can be consulted on the number of staff members that opened a simulated phishing mail and clicked any links in it. Security training and awareness info is provided to all employees on a regular basis.&nbsp;<h2>Conclusion</h2>Since there is a lot of money going around in banks, they will always be a target for hackers. For the banking industry, credibility and trust are the cornerstones. A data breach could easily lead their customer base to move their business elsewhere. By conducting regular security checks, banks can identify and fix vulnerabilities before they are exploited.&nbsp;

Interested in how security testing can help your organization?

The financial sector is about 300 times more vulnerable to cyber-attacks than other sectors. By conducting regular security checks, banks can identify and fix vulnerabilities before they are exploited.&nbsp;

Security testing for banking industry.jpg

The importance of phishing awareness

The recent cyberattacks in the cities of <a target="_blank" rel="noopener noreferrer" href="https://www.brusselstimes.com/technology/333018/city-of-antwerp-hit-by-cyber-attack">Antwerp</a> and <a target="_blank" rel="noopener noreferrer" href="https://vrt.be/vrtnws/en/2022/12/12/city-of-diest_s-servers-fall-victim-to-cyber-attack/">Diest</a> have once again emphasized the importance of IT security. The attackers used phishing to get inside the system and to steal personal data. But what is phishing and how can we help you preventing it?&nbsp;<h2>What is phishing?</h2>Firstly, what do we mean with it? Phishing is a method where someone contacts a target pretending to be someone else. For example, a close personal contact, a commercial company or a representative of a government institution. The objective is to get people to reveal sensitive information such as credentials, bank or credit card details. Such an attack can have devastating results going from ransomware attacks, revealing of sensitive data, identity theft, financial loss …&nbsp;<h2>History</h2>Its origin can be traced back to the 90s when hackers targeted members of American Online, a provider of internet access. By stealing user details, including username, password and other personal information, they were able to retrieve and misuse credit card information. Since then the practice has become widely spread. According to&nbsp;<a target="_blank" rel="noopener noreferrer" href="https://www.brusselstimes.com/justice-belgium/208033/belgium-4th-in-world-for-cybercrime">The Brussels Time</a>, Belgium ranks fourth globally for cybercrime density, with phishing as the most common cybercrime.&nbsp;<h2>Different types</h2>Email seems to be the most popular medium. But scammers have become more creative and started using other methods.&nbsp;For example these ones:<ul><li>Vishing and smishing Vishing is where scammers contact the target via phone, using their voice. Smishing is the use of text messages with deceptive content.</li><li>Spear Phishing An attack targeting a specific person or group of people. Generally, staff and IT managers with higher access levels.</li><li>Clone Phishing Related to spear phishing but instead of sending false mails, the scammer copies authentic mails and changes the link from the original mail with a new malicious link.</li><li>Pop-up Phishing Placing of code in a pop-up when visiting a website. For example, a message asking to allow notifications, when the user clicks ‘allow’, malware will be installed.</li><li>Calendar Phishing Fake calendar invitations with phishing links.</li></ul>&nbsp;<h2>How to prevent phishing?</h2>As it is becoming more widespread, it is key for companies to be protected against these practices. The best way to do so, is firstly to implement appropriate technical measures and secondly, to build a positive security culture among employees.Some examples of technical measures are a well configured firewall, automatic filtering of phishing mails, multifactor authentication, monitoring, etc. Besides this, there is also the security culture to consider, the human factor. According to a study from Verizon in 2022, 82% of breaches involved a human element. This includes incidents in which employees expose information directly (for example, by misconfiguring databases) or when making a mistake that enables cyber criminals to access the organization’s systems.&nbsp;<h2>Our security solution</h2>At Brightest we focus on two things. On the one hand our security defense solutions (application, API, mobile, network). On the other hand, the phishing aspect and the awareness of users.Since last year, we partnered with&nbsp;<a target="_blank" rel="noopener noreferrer" href="https://www.knowbe4.com/">KnowBe4</a>, a company co-founded by Kevin Mitnick. As ex-hacker he turned white-hat, in 1983 he was convicted for hacking the Pentagon. Mitnick is now active as Chief Hacking Officer of the company and knows the importance of security. In other words, the poacher turned gamekeeper. KnowBe4 is the world's largest integrated platform for security awareness training combined with simulated phishing attacks.In a nutshell, we start with a simulated phishing attack to measure the phish-prone percentage. This means the percentage of how many employees click on phishing mail content. Which is the starting point to improve by awareness training and follow-up simulated attacks.

Interested in how our security solution can help your organization?

The recent cyberattacks have once again emphasized the importance of IT security. The attackers used phishing to get inside the system and to steal personal data. But what is phishing and how can we help you preventing it?

Security testing.jpg

How can OWASP help you with application security?

'Hackers are having a field day with cheap smart appliances?', ‘Facebook data from 3 million Belgians sloshing about on the internet’, ‘Client data of Dutch and Belgian online shoppers put up for sale on the internet’, ‘Cyberattack on Defence Ministry and PM’s websites', … The list of articles related to application security and data protection is getting longer every day. It is, more than ever, a hot topic for developers and testers to secure applications against malicious practices. To keep up with the latest developments in security risks and solutions, we can highly advise the OWASP standards.&nbsp;<h2>OWASP whut?</h2>Firstly, what is OWASP? Open Web Application Security Project, also known as OWASP, is an open-source project that provides free information on application security. The OWASP foundation describe themselves as:“A nonprofit foundation that works to improve the security of software. Through community-led open-source software projects, hundreds of local chapters worldwide, tens of thousands of members, and leading educational and training conferences, the OWASP Foundation is&nbsp;the source for developers and technologists to secure the web.”Every few years OWASP releases a top 10 of vulnerabilities, a broad consensus about the most critical security risks to (web) applications. It’s an ‘awareness’ document for companies to include in their processes, in order to minimize the risks. To better understand the subject, let’s look at an example.&nbsp;<h3>For example: ‘injection’</h3>One of the items in the top 10 is ‘injection’. Let’s say you are using a website and you click on a product. In the background, the application can send a SQL query to the database like this:SELECT Product_Name, Product_Description FROM Products WHERE Product_id = 123In this case, the user will receive the name and description of the product with id 123. Pretty straightforward. Now, let’s assume that you intercept that query, slightly modify it and send it to the database like this:SELECT Product_Name, Product_Description FROM Products WHERE Product_id = 123 OR 1 = 1In the above case, we have added the ‘OR 1=1’ statement to the query. One equal to one is always true. So if we send that query to the database, we would get a list of ALL the products. Even items that were maybe hidden or not available to our user profile.And we could even be more creative. Let’s say we would again modify the existing query and merge it with another query:SELECT Product_Name, Product_Description FROM Products WHERE Product_id = 123 UNION SELECT Username, Password FROM Users&nbsp;By adding the additional Union query, we could get a hold of all the usernames and passwords of the application. Or we could just as easily ‘DROP’ a table and by doing so, make the application fail.&nbsp;<h2>The essence</h2>Without going into detail on how to protect your application against these different kinds of attacks, it is clear that developers and testers need to be aware of these risks. They&nbsp;should know how to secure applications against them.At Brightest we are investing a lot in our <a target="_blank" rel="noopener noreferrer" href="https://brightest.be/solutions/security-testing">security&nbsp;solution</a>. We strongly believe we can deliver better quality if the vulnerabilities of the application are also tested and secured. If you want to know more about this topic, please contact us or register for our training on <a target="_blank" rel="noopener noreferrer" href="https://academy.brightest.be/courses/introduction-to-web-application-security/">web application security</a>.

The list of articles related to application security and data protection is getting longer every day. To keep up with the latest developments in security risks and solutions, we can highly advise the OWASP standards.

Security.jpg

Gijsbrechts

Cost-efficient software testing. Where to start?

The single most common misunderstanding regarding software testing is that it is an avoidable cost. Organizations are often unable to manage testing in an effective yet efficient way. This requires an initial investment. So, the million-dollar question arises: when does an organization need to make this investment and where to start?&nbsp;<h2>What is a reasonable cost for software testing?</h2>It is very hard to advise on one single number to express the cost for software testing.&nbsp;From our experience, we think that there is one way to decide if costs spent on software testing are reasonable. Compare the cost of software testing in relation to the cost of production incidents.&nbsp;Software testing should always bring financial benefits when developing software applications.&nbsp;<h3>Cost of poor quality</h3>The cost of poor quality can be very complex to define. Defining the cost of fixing production incidents, is something every organization should be able to do for itself, considering their specific situation. In the world we currently live in, creating software&nbsp;first time right&nbsp;becomes more important than ever before. F.e. a mobile application being launched for the first time. If it doesn’t function properly, the end user will never use it again.&nbsp;<h3>The relative cost of defects</h3>In the graph below we see how the relative <a target="_blank" rel="noopener noreferrer" href="https://tryqa.com/what-is-the-cost-of-defects-in-software-testing/">cost</a> to correct a defect is much higher towards the end of the software delivery life cycle. You will end up paying three or even four times more when addressing a software defect during the ‘test stage’. The cost of fixing an incident in a production environment, is several times higher.&nbsp;<figure class="image image_resized" style="width:75%;"><img src="https://brightest-corporate-website.s3.eu-central-1.amazonaws.com/image_8ef55fa89d.png" alt="Chart, line chart

Description automatically generated"></figure>&nbsp;<h3>Shift left</h3>It seems common sense to focus on the early stages of software development and thus prevent defects as much as possible.&nbsp;In our experience, the only qualitative measure is the number of defects found before testing, being considerably higher than the ones found during the testing stage. For many teams or organizations this requires a different mindset, but it does not require magic. This does not mean it is an easy process. If crafting excellent software were easy, there would be no need for any kind of verification or validation.To explain shift left in one phrase, the simplest would be to state that testing should not be postponed until the last few days before a release. It should&nbsp;shift&nbsp;to the&nbsp;left&nbsp;on the project timeline. The main goal is to test&nbsp;early&nbsp;and&nbsp;often. So, this does not mean testing towards the end of the development cycle is forbidden. These test stages should still be performed as usual, but because you prevented or found most issues earlier on, they will be smaller and faster to solve.&nbsp;<h2>How to get started with cost-efficient testing?</h2>To be able to make your software testing as cost-efficient as possible, your organization needs a tailored and solid foundation. And besides that, a clear organization-wide software testing strategy. The best way to create this view, is to look at the organization’s processes, methods, people and tools that are part of the software development lifecycle. Then it comes down to a simple, yet clear statement: first move well, then move fast.We found that the best way to create such a solid foundation, is by taking an&nbsp;outside-in view.&nbsp;You get a broader view on your software development organization and software testing activities. By looking at the organization’s specific needs, available budget and the needed maturity level, it is possible to create a tailored approach based on best practices. At Brightest, we have made it our mission to create innovative solutions to enable organizations realize their quality objectives. Our way of approaching this is by performing an assessment, which we named&nbsp;BrightScan.&nbsp;<h2>BrightScan</h2>A <a target="_blank" rel="noopener noreferrer" href="https://www.brightest.be/solutions/brightscan">BrightScan</a> is a highly effective assessment,&nbsp;executed by a team of specialists. It provides an objective analysis of an organization’s current software quality and it deduces future evolution initiatives. It allows organizations to improve their test maturity and time to market while reducing their quality costs.&nbsp;<h3>Efficient process</h3>Over a period of two to four weeks, we conduct online surveys and stakeholder interviews. This to create a complete overview on the strengths and weaknesses of the current (test) organization. Depending on the need, we focus on the full process (beyond testing) and more technical matters. After this analysis a roadmap is created that highlights quick wins and defines short and long-term goals&nbsp;and&nbsp;improvements. We aim to link each goal to a measurable value for the organization.&nbsp;In addition,&nbsp;we give them an idea of the Return On Investment (ROI) of each improvement. What is left is the implementation of this roadmap. Organizations can start implementing&nbsp;this roadmap&nbsp;themselves&nbsp;and/or&nbsp;hire&nbsp;our expertise to guide&nbsp;them&nbsp;through&nbsp;their&nbsp;transformation.&nbsp;Ready to bring tour software development organization towards a higher level? A BrightScan can be conducted for any type of organization, from start-ups to multinationals. Pricing for a BrightScan depends on the complexity of your organization.

For more information or a quote, simply contact us!

Organizations are often unable to manage testing in an effective yet efficient way. This requires and initial investment. So, the million-dollar question arises: when does an organization need to make this investment and where to start?

Software testing experts.jpg

6 (wrong) reasons not to hire testers

For us, hiring a software tester seems the most obvious thing to do when a company develops software. Many do so, but a surprising amount of them don't. Some of these companies do not believe in the added value of testing. Even though, they see the importance of having a quality product. In this blog you can read about the most common excuses we have heard for not hiring testers. Spoiler alert: they are wrong.&nbsp;<h2>1. Lazy developers cause bugs</h2>Ever heard arguments like these? “If we hire&nbsp;a software tester, developers will get sloppy and write buggy code.”,&nbsp;“They won’t unit test or peer review anymore.”,&nbsp;“If we don’t hire testers, we can force the developers to write correct code in the first place and focus on unit testing.”Well, if you think this is true, you either have never written code, or you are strangely dishonest about what writing code is like. Bugs,&nbsp;by definition, leak out because developers didn’t see them in their own code.Just think about the time when you’ve written an article, whitepaper or thesis and you had someone reviewing it.&nbsp;We bet they found a few spelling errors or missed commas, even though you’ve read it over and over again yourself.&nbsp;<h2>2. Testers find too many bugs</h2>If you think your testers are really reporting too many insignificant bugs, give them guidance. Don't ridicule their effort or disregard their bug reports. Explain the requirements you're trying to achieve and the known (and acceptable) limitations of the system.&nbsp;<h2>3. Our developers can fix bugs in a second</h2>OK, this is somewhat true. Bug fixes can be deployed much faster nowadays, but don’t underestimate the cost of fixing a bug.Firstly, you might introduce even more bugs while fixing the first one. Secondly, all the time spent on fixing bugs, is time lost for developing new features. And finally, don’t forget about the bad impression you will make.&nbsp;<h2>4. The users will test the software for us</h2>Let’s see how this might go down as a ‘testing methodology’:<ol><li>When development is about halfway done or they say they are done, release the software without any testing</li><li>Repeat this step 8-9 times</li><li>Call one of these versions the ‘final version’</li><li>Release .01, .02, .03 versions every time a bug is reported and/or going viral on Twitter</li></ol>The only result you will get out of this is that users think the software is buggy and unreliable. The worst thing about this way of testing is the bad impression you will make. For the users it feels like nobody had even done a minimum amount of testing, to make sure the basics work. The low perceived quality of the product turns them off and maybe for good.&nbsp;<h2>5. Good, qualified people don’t want to be a software tester</h2>Painful as it is, it’s very hard to hire good testers. The only thing you can do about it, is to recognize it exists and deal with it. We have some suggestions to do so:<ul><li>Treat testing as a serious career step&nbsp;in your company. A move up from, for example, support or any other role they did before.&nbsp;</li><li>Don’t treat testers as second grade developers who just weren’t good enough to be real developers. This will demotivate testers who really love to test software and are good at it.</li><li>You need to offer testers a competitive salary. If you pay your testers way less than your developers, your testers will request a transfer to development or even leave your company.&nbsp;</li><li>Allow testers to develop their careers and technical skills&nbsp;by following trainings and courses.&nbsp;Encourage them to develop automated test suites using programming tools and scripting languages, install and configure test environments, … Nowadays, a tester can’t really do without these skills anymore anyway. Everything needs to move faster every day.</li><li>Hire experienced external testers. They come with recent knowledge about the latest testing trends, which enables them to work more efficiently. It’s interesting and inspiring for your internal testers.</li></ul>&nbsp;<h2>6. Testing is expensive, I can’t afford a software tester</h2>This argument is the easiest to refute. No matter how hard it is to find testers, sadly enough, they are still cheaper than developers.If you don’t hire testers, you’re going to have developers, analysts or business doing all the extensive testing. And while they are testing, time and effort is lost on development, analysis, or finance for that matter.&nbsp;In such cases, developers, analysts and business treat testing as a lesser priority. They rather do their own job and who can blame them? They are not actual testers so, lots of potential bugs remain in the software. The bugs who are found after the go-live or in the latest stages of the software development life cycle create a very high effort and cost. Besides that, they eat away time, effort and money from development, analysis, …Finally, if you think it’s bad when a software tester leaves your company, wait until you see how hard and expensive it is to replace a star developer. They get sick of spending lots of time on extensive testing before the release and move to another more professional company with testers. Saving on testers is not saving your company any money or time.&nbsp;

Interested how we can help you?

Many companies don't believe in the added value of testing. Even though, they see the importance of having a quality product. In this blog you can read about the most common excuses we have heard for not hiring testers. Spoiler alert: they are wrong.

Frustrations.jpg

<h1>Blog</h1>Listen to what makes us get up in the morning and makes us smile at work.Some fun facts and some business insights.