Today, however, despite a growing need for agile and efficient testing, legacy QA models are struggling to keep up with cloud-native environments, fragmented teams and rapid release cycles.

And this, says Mandla Mbonambi, CEO of Africonology, introduces a new era of software testing using AI and automation to prioritise tests and analyse vast quantities of data. It is also, he says, introducing quality, security and governance risks.

“The benefits of AI in testing automation and QA are that it allows teams to move incredibly rapidly,” he says. “Companies benefit from faster automation processes, and their productivity increases exponentially. AI is also capable of analysing the data to detect defects or coverage gaps, and it can provide teams with high-risk scenarios or recommend additional tests based on its analyses.”

The Capgemini World Quality Report 2024-2025 was quick to highlight the impact of AI on the industry, emphasising its ability to optimise test coverage, reduce human error and introduce intelligent automation.

The study found that an impressive 68% of companies are using AI, with 72% reporting faster processes as a result.

The technology is changing the testing story, moving it away from an after-the-fact process that discovers unexpected errors and frustrates teams and deadlines alike. AI enables testing in near real time as models continuously analyse code throughout the development process, and they can be integrated into development and operations from the outset.

“AI models can learn, they can predict errors that crop up regularly or where they’re most likely to occur,” says Mbonambi. “They turn testing into a smoother part of the process, making it proactive and immediate instead of reactive and defined by ticking boxes. They also allow for self-healing, where the automation can detect when a test will break, find a resolution, and then apply the update so the test still passes if the business behaviour remains valid.”

Self-healing has the potential to minimise failures caused by minor changes and reduce the monotony burden on testing teams – talented humans now have more time to prioritise exploratory testing or more complex tasks.

The technology gives people the space to become high-quality architects, defining risk models, guiding AI, and interpreting patterns, rather than just running tests.

“There are agentic platforms that now can take on a lot of the heavy testing grunt work with minimal human input, capable of acting almost like testing interns that fortunately don’t get tired or frustrated,” says Mbonambi. “It sounds too good to be true, which unfortunately it can be – while AI has immense value in the QA environment, it also introduces risks that have to stay top of mind.”

Just as AI in the workplace tends to hallucinate or overcompensate, the same risks apply in testing. Some of the most common problems include false positives and false negatives, which add to testing noise rather than minimising it, an over-reliance on automation that impacts skills and awareness, and data privacy and security.

Then there’s the reality that AI models are still black boxes – teams don’t have visibility into the AI decision-making process and don’t know why some tests are prioritised while others are not.

“Bias, security, private information, limited guardrails and governance that’s battling to keep up with the pace of change, are very real concerns when it comes to introducing AI into the testing environment,” says Mbonambi. “Right now, as teams learn how to use and optimise AI in testing better, it’s important to remember it is a tool designed to augment the process. People are needed to validate AI output and make release decisions and, very importantly, become the guardrails for data privacy and explainability.”

This doesn’t mean AI is too risky, just as it doesn’t mean AI is the perfect solution to every testing problem.

Right now, AI is as much in its infancy as its use cases, which means testing with AI models and tools should be considered and balanced. Humans are essential, but so are the tools that lift the burden of complexity and deadlines.

The recently concluded intensive 8-week online programme, trained 100 university students, emerging innovators, and tech enthusiasts.

Participants were equipped with critical software testing skills, preparing them to play pivotal roles in maintaining the quality and security of software products.

The programme was implemented through the Fintech Development and Advocacy Initiative arm of FSI, a platform dedicated to facilitating financial services innovation in Nigeria.

The Software Testing Programme aims to bridge the gap between academia and the financial services industry by offering hands-on, practical training tailored to market demands.

Speaking on the partnership and success of the programme, Muyiwa Asagba, Managing Director, Digital Commerce and Merchant Acquiring (Interswitch Inclusio) said:

“Innovation thrives when young minds are given the tools to succeed, and Interswitch is proud to sponsor this initiative, which aligns with our vision of nurturing a digitally inclusive future. By investing in these talents and providing them with practical, industry-relevant skills in software testing, we are not just enhancing the software testing ecosystem but also nurturing a generation of innovators who will shape the future of financial services in Nigeria and beyond. Initiatives like this reaffirm our commitment to promoting a digitally inclusive society while positioning Interswitch as a catalyst for innovation across Africa.”

Participants gained practical expertise in software quality assurance, addressing critical industry needs while bolstering their readiness for Nigeria’s burgeoning technology landscape. A standout feature of the programme was the recognition of top-performing participants, five of whom secured internship opportunities, giving them invaluable real-world experience and a head start in their careers.

Aituaz Kola-Oladejo, executive director, Financial Services Innovators (FSI), highlighted the programme’s transformation impact.

She said:

“We are thrilled to announce the successful completion of our 8-week Fundamentals of Software Testing course, which empowered 100 youths, 90% of whom are students in tertiary institutions. This training underscores our unwavering commitment to youth empowerment through education and skills development. Our goal is to equip young people with the knowledge and tools they need to thrive in future technology-driven careers, enhancing their employability and positioning them as globally competitive professionals. We extend our heartfelt gratitude to Interswitch for sponsoring this 3rd Cohort. Their support reflects a strong commitment to advancing technology ecosystem initiatives that drive national progress and innovation.”

By championing initiatives like the Intensive Software Testing Programme, Interswitch reinforces its position as a leader in driving technological advancement and empowering the next generation of African innovators.

This collaboration not only strengthens the company’s reputation as a catalyst for innovation but also fosters goodwill and loyalty within the tech ecosystem, paving the way for sustainable growth in Nigeria’s financial services landscape.

KaneAI comes with an innovative approach to creating, debugging, and evolving end-to-end tests using natural language, promising to enhance how teams manage and execute automated testing.

Automation testing is an important aspect of software development, but it often encounters limitations. Traditional test automation tools are frequently unable to keep up with rapid development cycles, leading to fragile tests that require constant maintenance. 

Even low-code/no-code solutions can falter at scale, leading to challenges in meeting the growing demands of modern testing.

KaneAI by LambdaTest is the first AI Test Assistant of its kind, featuring innovative capabilities like AI-driven test authoring, management, and debugging. Specifically designed for high-velocity Quality Engineering teams, KaneAI allows users to create and refine complex test cases using natural language. 

This drastically reduces the time and expertise needed to implement test automation, making it accessible for various team members to contribute to the testing process.

Combined with built-in features like intelligent test planning, AI-powered test healing, and advanced conditional assertions, KaneAI supports complex workflows and ensures comprehensive test coverage.

Unlike traditional low-code/no-code solutions that hit scalability limits, KaneAI provides 2-way test editing features that enable users to either author in code or Natural Language. 

In addition, it allows multi-language code export across all major frameworks along with unique Instruction-to-Code and Code-to-Instruction translation features. This enables effortless maintenance of scale tests and ensures that even the most intricate testing needs are met.

KaneAI also revolutionises the debugging process with its AI-powered test observability and real-time RCA (Root Cause Analysis) capabilities. This helps large-scale distributed engineering teams minimise application downtime and accelerate release cycles, without compromising on the product quality.

Further KaneAI integrates seamlessly with existing workflows, supporting popular tools such as Jira, Slack, GitHub Actions, and Microsoft Teams, making it an invaluable addition to any testing toolkit.

“Over the past 6 years, we have listened to feedback from the users on how to solve their testing challenges. KaneAI is the result of our team’s innovative approach to address that. The engineering and product team has spent over a year building this revolutionising product and pushing the boundaries of what is possible in quality engineering. 

They ensured that every aspect of KaneAI could meet the real-world challenges that testing teams face daily. This journey was about developing an AI-powered test agent and reimagining what test automation could be,” said Asad Khan, co-founder and CEO at LambdaTest.

“KaneAI exemplifies LambdaTest’s unwavering commitment to revolutionising quality engineering. Having led technology firms for two decades, I have seen software development teams struggling to keep up with the fast pace of change and remain agile as they deliver top-tier products. KaneAI is a game-changer and addresses large-scale challenges for quality engineering teams. 

Through this product, LambdaTest disrupts the legacy testing ecosystem. NLP-based test authoring fundamentally breaks through the traditional testing workflows and empowers product managers, Developers and testers to seamlessly integrate continuous testing into the DevOps workflows,” Sandeep Johri, CEO of Checkmarx stated.

With the introduction of KaneAI, LambdaTest has established itself as a comprehensive solution for all end-to-end software quality engineering needs. From test planning, authoring, execution, analysis and reporting, LambdaTest now covers all functions along with its core capabilities of providing cloud environments for test execution on real devices and browsers. 

Additionally, AI-powered test intelligence provides valuable insights, ensuring a robust and integrated approach to quality assurance.

KaneAI’s private beta is currently available. Quality engineering teams interested in staying ahead of the curve can sign up for early access at KaneAI.

Tinah started her tech career with Cyberspace Network Limited as part of the technical product support team that pioneered and contributed to the distribution of retail 4G LTE network in 2016.

Her spark for product quality ignited which led her to join ALAT, Nigeria’s First Digital Bank.  During her time at ALAT, Tinah’s software testing career emerged as a Manual Software Tester and she contributed immensely to the QA processes through the creation of test plans and test cases, which also helped increase user experience.

The success achieved with ALAT propelled her to up skill by undertaking a certification, in both Manual Testing and Test Automation.

Tinah later joined Enlumi Data, a SaaS company that produces an array of solutions for businesses to drive quality efforts across the software development lifecycle. While working at Enlumi, the team created a platform called “Lumi Business” to empower SMEs with variant tools like Inventory management, Loyalty Management, Business Analytics and a lot more to aid the growth of their business.

Over the course of her career, Tinah Peters have developed competencies in the use of Java language, automation tools like Selenium, Postman, K6, Testrail, and bug reporting tools like Jira, Notion, and Trello while driving product quality improvement using agile testing practices, {SDLC}.

She played an integral role in designing software testing framework and setting up QA standards and processes to drive product quality improvement.

At Patricia Technologies Limited, Tinah collaborates with the software team to execute automation script and manual tests on Cryptocurrency applications.

She plays a strategic role in the development of test plans, test cases, maintaining QA standard and the review of PRD documents from the product team to ensure 100% test coverage before the deployment of applications to users.

In this interview Tinah Peters share her experience as software tester; technical expertise, and experience working with tech startups and strong leadership abilities which have enabled her to contribute to the development of world class products within the tech ecosystem in Nigeria and Africa.

Can you tell us how you got into software testing?

Tinah Peters: I have always been a tech enthusiast, my experience been part of the technical product support team exposed me to understanding the importance of software, its phases and how this customer’s use the finished product. On the other hand, supporting customers on issues regarding product sparked a flare and my curiosity about software quality and how it impacts user’s experience. Thus, the rest is history.

Why do we need software testing?

Tinah Peters: Software Testing is imperative in every organization; the need cannot be overemphasized . Early software testing identifies bugs found within a line of code which can pose to be a threat.

We understand that the quality of product must be a contributed effort from all team member in line with the QA & ISO standard but the need for an end-to-end isolated test is not negotiable for second validation before any release.

Hence, the need for a software tester. However, the products under test must satisfy the requirements which is customer centric before a final documentation can be issued out for deployment.

What are the key challenges that software testers commonly face, and how do you overcome them?

Tinah Peters: In the course of my work, I have found the following as key challenges software testers face. First, inadequate knowledge of what is expected of the product and what it intends to solve: It is an ideal practice to incorporate the software tester from the start of the project especially when conversations and ideas are shared in the initial stage. This help the tester to be cognizant of what the product intends to solve and what the expected outcome should be.

Secondly, time constraint for Testing can also be a key challenge: Realistically, development sometimes takes a substantial time and leaves the tester with very short time to test.

Sometimes this is inevitable however, the solution here is to break task into manageable and feasible timeframe, set deadlines according to priority. Overall, a self-imposed deadline is usually the best approach and would just do the Job.

Thirdly, insufficient or missing information on the product requirement: Challenges like this commonly happens when conversations or scope discussed with clients/stakeholders regarding the project is more verbal and less written which down the line affects every team member working on their deliverables. So it is advisable to have all conversations documented in order to avoid missing out important point and aspect of the stakeholders expectations.

Fourthly, Lack of communication which impedes software testing. So, it is important that communication is taken seriously and wholeheartedly to avoid any communication gaps that will delay the deliverable of the projects.

The few solutions I believe software testers can adopt include but not limited to; Communication should be consistent; tester should not be afraid of communicating their opinions and observation.

Tester and Developer must build and maintain a communication lifestyle. Defects identified should be concise and clear when communicating which means requirement must be thoughtful before sent out.

Also, collaboration tools should be helpful and easy to use, and incomplete or change of requirement should be communicated to all team members.

How has the role of software testing evolved with the shift towards agile and DevOps methodologies?

Tinah Peters: Shift-left testing approach simply just encourages testing application early, right from the start of the project. As testers integrate or incorporate testing activities right from the start, it allows organization address defects, pro-offer valuable insight that sharpens the development process yielding to improved product quality and faster development.

Also, fusing early testing activities aids the software development team to invest effort on more proactive approach to providing quality on their code, speed up testing while hunting bugs as early as possible in the code. This process fosters confidence in the product and faster deployment.

Can you share a success story where effective testing significantly contributed to the success of a project?

Tinah Peters: In my present position, I recall detecting a UI flow defect while carrying out an end-to-end automation testing on our web application for withdrawals. I realized that the UI does not communicate the breakdown of the fees charged and this could be a potential problem for our users. So, I reached out to the product manager to inform him of the issue and suggested a possible flow that could work to review for adoption.

Thereafter, the product manager quickly communicated the initiative to the necessary stakeholders, as well as the product designer for a new design flow. This aided the backend engineer to make the necessary changes to the code base.

After a successful change was made then I carried out a regression test to re-validate the new adjustment before deployment. Having spotted that defect was appreciated which of course contributed to a successful success story for that release.

What are some common misconceptions about software testing, and how would you address them?

Tinah Peters: There are quite a few misconceptions, but let’s look at just a few:

Quality checks are for Tester only: The misconceptions that testers are overseers of all the application, code and everything about technology makes it more surprising. Just the way we ensure that there are less bugs in the application, we also believe that the developers would not develop terrible codebase that would cause the project to fail.

We do not dispute the need for testers to gate keep the application, but it is also every one’s responsibility to ensure that quality is applicable to everyone involved in the project. The earlier people understand that tester ensure that application is testable, and quality is maintained; the better high quality product release can be achieved.

Tester should be involved in only post development: This is another misunderstanding about software testing which if still practiced in organization can be a disaster. Involving QA at a later stage simply mean that the tester would heavily rely on what is communicated by the developer that means that the tester is conditioned to what he or she believes was built by the developer.

This kind of test can be a big risk to the project, because the time given to tester are usually scrunched. Tester’s need to have equal time as developers to test as one way forward to achieving a good and better-quality result.

Anyone can Test: This is one the biggest myth about software testing. As we know that anyone can become anything they want to be e.g. From a designer to a CEO in a company so it gives that impression that testing can be done by anyone by just clicking around.

Whereas the truth lies behind the ability to handle any emotional involvement when issues are classified as ‘working as expected’ because codes dictate behavior to a very large extent. Like James Bach would say ‘Pretty good testing is easy to do (guess that is partly why some people like to say ‘testing is dead’ — they think testing isn’t needed as a special focus because they note that anyone can find at least some bugs some of the time). Meanwhile, excellent testing is quite hard to do.’

In simple terms, not everyone can test, to be a good tester, you would need a specific kind of mindset to excel.

How do you approach creating test plans and strategies for different types of software projects?

Tinah Peters: First and Foremost, a well-designed test plan provides transparency of the testing activities which is shared to the associated stakeholders.

This document is expected to be dynamic and embrace changes according to the progression in projects which often always stays current.

There is no one size fit when creating test plans, but it is important to understand what the project intends to achieve to be able to craft a structured test plan. My advice would be to analyze the product requirement document provided by the product team to draft a comprehensive test pan.

Product Analysis: This is the point where other team member reviews the consolidated document and ask questions for clarity.

Design Test Strategies: This is where a strategy is crafted out which in view focuses on the project objectives and how these can be achieved. With a mindset of referencing the testing activities which is more like a “plan” to executing the test.

Defining Objectives: The objective must be concise and clear so that stakeholders understand what exactly would be tested and its expectation. This phase defines the goals and expected results of test execution. Since all testing intends to identify as many defects as possible, listing out the following such as performance, functionality will establish the exit criteria for the project.

Also, the scope of test, methodology, assumption & risk, mitigation plan, roles and scheduling should establish successful test deliverable.

In the era of continuous integration and continuous delivery, how do you ensure efficient and reliable test automation?

Tinah Peters: In this era, the usual practice is ensuring consistent integration of written code to the repository created in the cloud. The continuous integration establishes processes and encourages testers to commit scripts/code frequently.

The more frequent automated scripts are deployed to the main branch for production use after there is an assertion that development & staging works as expected, the more the process demonstrates the need for continuous delivery.

Notwithstanding, further description considered for ensuring that continuous delivery is achieved are listed below though not limited to:

Integrating CI/CD: The usual practice for integrating continuous delivery which allows deployment at every change that passes your test case automatically establishes a high possible chance of using an advance level of test automation. While the Continuous integration implies a process whereby software developers are encouraged to always integrate every change made.

Ensure that each environment is bug free: Developing and maintaining script for each environment reduces the chances of having so much bugs which then increases the chances of improved quality software. Establishing this kind of development using flexible scripts accommodates continuous regression which guarantees efficient and reliable test.

Be Strategic in identifying and planning the preferred test case: This simply just encourages a strategy that helps in identifying what, how and when to test and who is testing the test cases.

The agile process has kicked against delays that may be encountered and motivated steps made toward automated test to be broken down into smaller component for re-usability for multiple test cases.

In summary, software testers need to develop excellent test scripts for their tests to stand any chance of an improved quality software.

What role does collaboration play between developers and testers in ensuring a high-quality product?

Tinah Peters: Collaboration between developers and tester cannot be under-estimated. The need for collaboration is an assurance to producing a high –quality product. When testers and developers work together seamlessly, there is an increased chance of building a team spirit, same goal drive, mutual understanding which leads to a more efficient, improved software and high-quality product.

I must say open communication and collaboration does the Job.

How do you prioritize testing efforts when faced with time constraints in a project?

Tinah Peters: This is an interesting question. I will attempt it this way: The simple way to do this is to implore self-discipline. You must understand the requirements and what is expected of the product. Let’s assume there are no test cases, make a list of the key features or critical functionalities.

Also, the ability to assess risk and dependencies that may likely be encountered.

You must embed time management skills into the process as this is key when prioritizing task based on project or feature.

Can you discuss the impact of emerging technologies, such as AI and machine learning, on software testing practices?

Tinah Peters: The introduction of emerging technologies such as AI has undeniable impact in revolutionizing how software applications are tested. Nonetheless, I would say that AI has aided trouble shooting and made working process more seamless which saves time.

However, players in this industry cannot take out the part that the challenges surrounding the use of AI poses a threat and security concern on the product under test. As the AI-driven testing heavily relies on test data which may need to be critiqued for accurate testing since the information is retrieved from the public. Some questions are still presently asked does the advantage outweigh the disadvantage.

How do you stay updated on the latest trends and advancements in the field of software testing?

Tinah Peters:  To stay abreast on latest trends, there is a need to keep an open mindset that is ready to embrace change. Also, you should join onsite and off-site community to learn more trending tools. You can’t play down the need to take up certifications online and explore new courses.

Read up blogs, newsletter and articles in the field, and experiment new techniques and tools.

Can you share insights into balancing between manual testing and test automation in a testing process?

Tinah Peters: I would say finding the right balance between manual testing and test automation can be sometimes difficult because there are factors surrounding these, which can be the following: complexity of the project, scope, requirement, quality expectation, number of skilled testers, and time of delivery.

Nevertheless, it is more appropriate to start a manual test to understand the system and what the expected outcome would be. Once that has been established, then test cases can be crafted out based on your understanding which then proceeds to prioritizing the test cases.

It is not a rocket-science that automated test can only be successful when there is good understanding of the expectation via exploratory. Hence the need to strike a balance.

Guidelines are set aside to ensuring this expectation are met. Automation can take place once testers are able to establish stable and critical functionality of the system. In all of these, manual testing cannot be eradicated as it somehow complements in the aspect of features that are dynamic, difficult and subject to automation.

What strategies do you employ for testing in different environments, such as web, mobile, and desktop applications?

Tinah Peters: My usual approach is applying functional and non-functional test strategy when testing different environments and applications such as web, mobile and desktop.

Not forgetting the need for automation using tools such as BrowserStack, Appium etc, to execute test on different devices and browsers. Furthermore, the need to mention the relevance of compatibility testing cannot be underrated when employing strategies for testing.

According to the ISO 90001 standard, quality should exceed expectation so that users are satisfied.

Can you discuss the role of exploratory testing and its significance in ensuring comprehensive test coverage?

Tinah Peters: The role of exploratory testing is not far-fetched as this kind of testing allows testers mimic the real-world usage, actions that would be carried out by users and the ability to find bugs in the application. The use of exploratory test encourages tester to be more tactful leaving tester to be more intuitive.

Exploratory can be used for different purposes for achieving a large test coverage in the following phases which are: requirement phase, development phase and finally the post release & maintenance phase. Meanwhile exploratory test is still performed, to ensure that it canopies the parts that the script was not able to cover.

In a nutshell, even if the application under test is automated using a script, the undeniable truth is that exploratory compliments test scripts to uncover hidden defects that was not covered.

How do you handle regression testing, especially in complex software projects with frequent updates?

Tinah Peters: As we all know the importance of regression and why it is necessary when changes are made. However, it is also important to mention that the number of time codes are updated should be equal to the number of times the test should be carried out.

There is no one size fit all as to how regression should be carried out, but it is imperative to outline how you would want to prioritize the test based on critical functionalities, continuous defect feature, and end to end features.

Now there are few steps that can be followed to achieving an excellent regression test; prepare for manual and automated test; identify which changes or upgrades on existing modules of the application will impact its functionalities and use manual and automated test accordingly.

Can you share your perspective on the role of performance testing in delivering a seamless user experience?

Tinah Peters: Every organization must embrace performance testing to increase the readiness of the application yet to be released. Benchmarks are placed to ascertain what the agreeable thread user should be when sent to the server, the time duration the request is sent and the response returned is very crucial in determining the performance, if it is above or below the benchmark.

It is advisable that functional testing must have been conducted successfully before proceeding to performance test such as load and stress to understand the application capacity under stress and normal condition.

Also, it is safe that testers can perform a scalability test based on the number of user requests and observe the returned performance response.

What advice would you give to organizations aiming to establish a robust and effective software testing process?

Tinah Peters: My advice to organizations is that they should have a mindset that plans to succeed. Organizations need to be open to change and ready to embrace the change as things revolutionizes.

In addition, having a plan for software testing will save you some fortunes, time and product failure. You need to adopt a shift left approach to start testing early for every features too.

In your experience, how does a strong quality assurance culture contribute to overall project success?

Tinah Peters: Going by ISO: 9001 Standard, organizations should put in place effective processes for unbroken product time after time.

In other words, strong quality technique must be adopted amongst teams from the start of a project to build processes that ensure that the outcome of a product meets the expected requirement.

In all, quality culture promotes consistency and efficiency.

It has been nice speaking to you.

Tinah Peters: Thank you very much for all you do in promoting tech ecosystem in emerging markets.

NGSTQB invites stakeholders in the Nigerian software ecosystem to a one-day Webinar under the theme: ‘The Role of Software Testing in Nigeria’s Digital Economy.  

Register here to participate.

NGSTQB is a leading organization for the Certification of Professionals in Software Testing in the West African country. 

It is also the local chapter for The TMMi Foundation, the architect and owner of the Test Maturity Model integration (TMMi) – a detailed and structured model for test process improvement and the world standard.

Stakeholders will leverage the NGSTQB’s one-day Webinar to discuss issues around Software testing in the country. 

Prof. Isa Ali Ibrahim Pantami, the Minister of Communications and Digital Economy will deliver the keynote address at the workshop.

Mr. Oliver Denoo, President International Software Testing Qualifications Board (ISTQB), will present the lead paper. 

According to the Global Market Insights report, the software testing market size exceeded USD$40 billion in 2020 and is estimated to grow at over 7% CAGR from 2021 to 2027.

Speaking ahead of the Webinar scheduled for 21st June 2022 at 9 am (WAT), Mr. Boye Dare, President of NGSTQB, said that the central objective of the workshop is to discuss the role of Software Testing in achieving Nigeria’s Digital Economy Strategy.

“The importance of software testing and quality assurance is highly valued in a software development cycle. Both processes refine the whole process and ensure the superior quality of the product. In addition, it reduces maintenance costs and provides better usability and enhanced functionality. When software testing signs and push the individual components, quality assurance attests to the product- Fit for the purpose.

“With Nigeria moving towards a more digitally embedded society, the influence of software is far more considerable these days. Software enhances the business prospects and evolves an intelligent world. In addition to the industrial /commercial impact, software plays a critical role in all facets of life today. However, all it requires is the smooth and fail-proof functioning of the software.

“Otherwise, the disastrous effects of software failures can have a crippling impact on the business and livelihood. During the workshop, we will explore the benefits of software testing and quality assurance for any business.

“The irrecoverable damages that software failure can cause are evident from the startling reports worldwide. For example, in 2017, a statement released by Tricentis revealed that global enterprises have lost 1.7 trillion in assets and affected 3.7 million people across the globe. According to a report by Synopsys, Inc. in conjunction with Consortium for Information & Software Quality (CISQ), the cost of poor software quality in the US in 2020 was approximately $2.08 trillion.

In addition, the gory tales of enterprises affected by software glitches appear in the news almost daily worldwide. The IT snags that created substantial financial losses in different business sectors and organizations such as British Airways, Facebook, O2 network are good examples of after-effects of software failure”.

How to participate:

The workshop is free, but you are required to pre-register using the link here or visit: https://www.ngstqb.ng/workshop/