Agile Testing Logo white

Have a bulletproof testing strategy and get rid of bug costs with us, with Agile!

Countless development hours are spent on bug fixes due to the lack of testing knowledge, testing resources and strategy, eating into Your profit.
These hours and money could be spent on new business value instead.

How we do it?

We don’t just teach, we work with
you in the field!

Technical and professional support will be there anytime you need it

What You get

Save up to 70% of the
time You currently spend
on bug fixing

Improve customer
satisfaction

A culture of ever
improving quality
and speed

Improved
profit ratio

Personal pride in
Your experts

What is UAT?
UAT is aimed at measuring the satisfaction of your customers and stakeholders. This level is primarily confirmatory, that is, the test is considered acceptable if it produces a successful operation. For example, the confirmatory aim is to detect bugs that can only be tested in the final production environment.

What is the expected result?
It determines whether the system is ready for the go-live.

How is it typically measured?
The number of bugs reported by users decreases.
To what extent automated tests cover functions and core processes.

When is it considered successful?
It is a business decision what percentage of bugs reported during UAT are actually addressed.
It creates go and no-go decision situations.
It is considered absolutely successful if proper testing does not result in any reported bug and all test cases run without error.

Implementation
Automated tests and test robots modeling end-user behavior

What is needed on the customer’s side?
Identified core processes
Test scenarios derived from user stories and test cases

Economic view
The cost of a given UAT test does not change if the conditions and the content of the test do not change.
There is a critical UAT test volume above which it is worth investing in an automated test with a higher cost threshold. The automated test must be changed if the test scenario (and/or user story) changes.
With automated tests, the unit cost of the test becomes less and less with each test run.

Prerequisites
Test scenario and/or user story

Managing feedback
Operational alignment of customer service and software development

What is Unit Testing?
Unit Testing is aimed at testing smaller components of a software at a code level, for example testing already existing methods and functions.

What is the expected result?
The test checks if the unit works as expected. In case of a method,it checks if the value obtained is the same as expected.

How is it typically measured?
With manual or automated tests where the value obtained is not the same as expected.

When is it considered successful?
The smaller components of the software work as expected.

Implementation
For example JUnit, PHPUnit

Economic view
It represents the lowest level of the code testing hierarchy.
With unit testing, when new development and testing elements are put together, regression errors are discovered together with minor coding mistakes made during development.
By using the unit test you will have a mistake to correct instead of a bug to be fixed and mistakes are cheaper. The bug is returned from the market, a mistake is discovered during development before it goes live.
As a result, no profit will be spent on bug fixing, no customer will be dissatisfied, and you will not face any brand damage.

What is needed on the customer’s side?
The developers are required to acquire competencies necessary to write unit tests.

Prerequisites
Identifying core processes (completed by Business Analysts)

Managing feedback
With the end of the iteration (sprint), the test results and the development team’s opinion are considered and a decision making process takes place about the resources that can be used for bug fixing in the next iteration.

Knowledge matrix
Coming soon

What is Integration/Interface Testing?
Integration/Interface Testing is aimed at searching for bugs created while putting together the modules. Also, it tests and checks the communication between two softwares or between the components of the same software. The Interface Testing is one of the most important tests to ensure smooth and safe communication between software components.

What is the expected result?
Communication between softwares and/or software components works as expected.

How is it typically measured?
With manual and/or automated tests

When is it considered successful?
It is considered successful if communication between softwares and/or software components works as expected.

Implementation
For example manually, with JMeter, Selenium, Silk Performer, or other automated tools. It depends on the application to be tested, whether it is web-based or a desktop application.

Economic view
With Integration Testing, a stable service is created ensuring that new solutions work well with existing components and it maintains customer satisfaction.
Integration Testing makes it safe to release new product versions that increase the number and frequency of returning customers and users. It is also optimal if it boosts retention.
Interface Testing helps different systems become well connected in a product which provides a complex service. With stable operation between systems, you avoid causing problems for your users, including compensation for damages.
Data leakage and data loss do not occur.

What is needed on the customer’s side?
Knowledge of interfaces
Integration procedures, rules and expectations to be established and monitored

Prerequisites
A comprehensive documentation of interfaces concerning business and technology
Business logic workflow between systems

Managing feedback
Employees responsible for the interface and integration and the development team are in close cooperation with the Product Owner.

Knowledge matrix
Coming soon

What is System Testing?
System Level Testing is aimed at checking the whole system. Typically it is Black-Box testing. Its primary objective is to increase the customer’s trust that the system meets comprehensive professional and business requirements.

What is the expected result?
The system meets the specification and the system design.

How is it typically measured?
It is typically measured with automated tests.

Bugs detected during testing:

  • location
  • frequency
  • impact

When is it considered successful?
Bugs are fixed or their frequency and impact are significantly decreased.

Implementation
For example with JMeter, Selenium, Silk Performer, or other automated tools. It depends on the application to be tested, whether it is web-based or a desktop application.

Economic view
By defining requirements more and more purposefully and following the agile methodology for product development, you minimize the waste resulting from overdevelopment. At the same time you also minimize the waste resulting from underdevelopment, which can be the source of several bugs at this level.

What is needed on the customer’s side?
Comprehensive knowledge of the business logic and the architecture of the product as well as of test tools.

Prerequisite
A clear list of requirements and their alignment with the continuous evolution of the product.

Managing feedback
It is a business decision how much of the bugs detected during system testing are actually addressed.

Knowledge matrix
Coming soon

What is Regression Testing?
Regression Testing is a type of software testing that checks whether a recent program or code change has adversely affected the already existing services. Regression Testing refers to the selection of all or a certain part of the test cases that are executed again to ensure that the existing functionalities work properly.

What is the expected result?
It provides a list that shows if there are any bugs in the service units that were previously running.

How is it typically measured?
With automated tests and the number of bugs detected during testing.

When is it considered successful?
The bug is detected before the user becomes aware of it.

Implementation
For example with JMeter, Selenium, Silk Performer, or other automated tools. It depends on the application to be tested, whether it is web-based or a desktop application.

Economic view
By defining requirements more and more purposefully and following the agile methodology for product development, you minimize the waste resulting from overdevelopment. At the same time you also minimize the waste resulting from underdevelopment, which can be the source of several bugs at this level.

What is needed on the customer’s side?
Coming soon

Prerequisites
Coming soon

Managing feedback
Coming soon

Knowledge matrix
Coming soon

 

What is Smoke Testing?
Smoke Testing is aimed at testing the critical parts of the software. It contains test cases where the failure makes further tests fail.

What is the expected result?
It gives a quick answer on whether it is worthwhile to test the current version of the software. If the testing is successful, the product can continue the next process step. QA experts can start testing and a version build can be released.

How is it typically measured?
Test cases selected in the test suite run without any error.

When is it considered successful?
Test cases selected in the test suite run without any error.

Implementation
Coming soon

Economic view
It makes the use of specific testing resources more efficient.
Builds with a high risk of bugs are not released in production.
Delivery speed will be faster because bugs are detected sooner in the value chain, so it will not result in extra resource allocation and problems.
It also makes the testing of high priority tasks more secure.

What is needed on the customer’s side?
Coming soon

Prerequisites
Coming soon

Managing feedback
Coming soon

Knowledge matrix
Coming soon

What is?
Random Sample Testing is aimed at testing a specific, targeted part of a software.

What is the expected result?
It is recommended to use it after code changes. Only those tests are run that target the features affected by the code change. This approach saves us time while verifying the correctness of the affected code.

How is it typically measured?
Test cases selected in the test suite run without error.

When is it considered successful?
Test cases selected in the test suite run without error.

Implementation
Coming soon

Economic view
Random Sample increases the experts team’s confidence in their work by ensuring that the Random Sample Testing of the product also runs without error.

What is needed on the customer’s side?
Coming soon

Prerequisite
Preliminary testing of previously developed codes or external systems

Managing feedback
Coming soon

Knowledge matrix
Coming soon

What is Security Testing?
Security Testing checks the resilience of the software against known attacks.

What is the expected result?
It examines if access can be obtained to the sensitive, critical parts of the software without permission.

How is it typically measured?
It is measured by running the test scenarios uncovering security gaps.

When is it considered successful?
When running the test scenarios, no access is obtained without permission and no security gap is found.

Implementation
A documentation on security test requirements

Economic view
Storing and using data used by the software becomes more secure.
The lincene and the software itself cannot be stolen or copied.

What is needed on the customer’s side?
Coming soon

Prerequisites
A documentation on security testing requirements

What is Load / Performance Testing?
It tests the load capacity/performance of the software under base, increased, and critically increased loads.

Achievable goals
To check how the system reacts to certain loads.

What is the expected result?
The performance limits and resource requirements of the software/system become clear.

How is it typically measured?
Those instances of the written test scenarios that can be run in parallel are run in bulk and simultaneously on the system while the system load metrics are monitored together with the performance of the test scenarios

When is it considered successful?
If the achieved constraints meet the requirements of the software (the software can stably handle the expected amount of parallel task load with sufficient responsiveness).

Implementation
Például Jmeter, Silk Performer

Economic view
It returns a result that enables the owner/operator of the software to satisfy their customers according to SLA.

What is needed on the customer’s side?
Coming soon

Prerequisites
A description / plan about the nature of using Load / Performance Testing
Preliminary load estimation
Seasonal impact if any
Scalability criteria/plan

Knowledge matrix
Coming soon

What is a test case?
A set of operations that are performed to check a particular function or functionality of a software application. A test case contains test steps, test data, preconditions, postconditions developed for a specific test scenario to verify any requirement. A test case contains specific variables or conditions.

What is the expected result?
It allows a QA expert to compare expected and actual results to determine whether a software meets the customer requirements.

How is it typically measured?
It is checked if there is a sufficient number of test cases for each function of the software that record the expected response to the different input states of the functionality.

When is it considered successful?
The creation of test cases has helped to improve the efficiency and quality of testing. It also increased the number of errors detected by the test cases.

Implementation
HP-QC

Economic view
Coming soon

What is needed on the customer’s side?
Coming soon

Prerequisites
Coming soon

Knowledge matrix
Coming soon

What is Automated Testing?
Automated Testing is performed without human intervention. Its technical background is varied: scripts, programming languages, special utility softwares. Automated Testing can handle large volumes of tests and test data quickly, making them suitable for performing tasks that manual tests cannot handle.

What is the expected result?
Such tests can be performed that are not feasible or economical to perform manually.

How is it typically measured?
With increasing efficiency and speed of testing

When is it considered successful?
Testing time/cost efficiency increases.

Implementation
Jenkins, Ranorex. JMeter, Silk Performer, Selenium

Economic view
Except for the development costs, it can be run for free.
I can perform instant reporting, e.g. warning, ticket, notification, which provide quick information.
It can be scheduled to run at times when it is the most ideal, e.g. no one is working on the software, so testing load does not take up users’ resources.

What is needed on the customer’s side?
Automated Testing competencies

Prerequisites
Test scenario
Running environment
Decision on where to run the tests (live/dev environment)
Who gets the information and in what way

Knowledge matrix
2

What is Checkstyle?
A set of syntactic rules defined by the development team, along which the written code should be formatted, including Lint.

What is the expected result?
The existing development team can perform peer-review more efficiently, as the code is easy to read due to the format written in the same way by everyone.
It is also easier to onboard new developers because the entire code base is written in a unified syntactic format, so there is only one set of rules to learn to read it.

How is it typically measured?
It is measured by checking if there is a set of rules for code formatting in the development team

When is it considered successful?
The development team has a set of rules for code formatting.

Economic view
The more uniformly the developers develop the software, the less room there is for making mistakes. This standardization does not kill the developers’ creativity. For example: If we write a Microsoft Word document together, it is recommended to use the same font style and size. The employees become more replaceable while the code becomes more easily transferable. It also becomes easier to integrate a new team member. Also, the code is more transparent when debugging.

What is needed on the customer’s side?
Principles set by the Architect/Lead Developer (the experts team might as well get involved).

Prerequisites
Coding standard within the experts team

What is Lint?
Lint is a developmental tool for building good developmental culture to control the specificities of the used programming language and recommend productive solutions.

What is the expected result?
Developers can get recommendations on productive ways to use the programming language in addition to or instead of the usual ways.

How is it typically measured?
It is measured by checking if the development team has Lint software and it is used in daily development.

When is it considered successful?
The development team has Lint software, and its use is a part of the daily routine. Also the experts team periodically discusses recommendations as they arise.

Economic view
The coding standard reduces the time for reviews, so code coverage can increase. As a result, the freed-up time can be reallocated without further time need. The mental burden coming from code legacy can be reduced.
Replaceability and the integration of a new team member is easier.
Knowledge transfer within the experts team is accelerated through standard coding practices. The experts team can react to potential bugs faster, making the whole development process faster and cheaper.

What is needed on the customer’s side?
Standards defined by the Architect/Lead Developer

Prerequisites
Available (community level) coding standards
Examining available tools (programming language, project, team preferences, etc.)

What is Code Coverage Testing?
A measure of how much of the production code is covered by tests.

What is the expected result?
It provides the stability of the code covered by the tests by guaranteeing that the expected functionality is preserved when the production code is modified.

How is it typically measured?
It is measured by using CodeCoverage tools to run the tests (e.g. JaCoCo).

When is it considered successful?
If at least 60-70% of the business-critical functionality is covered. It is even better if 60-70% applies to the coverage of the entire code base (while the coverage of the business-critical functionality does not fall below 60-70%).

Implementation
JaCoCo

Economic view
The optimisation of costs coming from the wastes of overdevelopment and underdevelopment.

What is needed on the customer’s side?
Goal setting depending on resources, time, market, product strategy, expected product lifecycle, and contractual conditions

Prerequisites
Knowing the profitability of the product in light of the expected testing costs and the planned code coverage

What is Branch Testing?
Branch Testing is less related to testing technology,. Rather, it is a method to reduce the possibility of errors.
Creating and following a branching strategy is important, without it development may include risks, e.g. conflicts resolvable and unresolvable by git, e.g. in case of automerge.

What is the expected result?
Coming soon

How is it typically measured?
Coming soon

When is it considered successful?
Coming soon

Implementation
Coming soon

Economic view
The branching strategy and the used tests can pre-validate the integration test, as a result of which resources are not used for relatively expensive tests whose focus elements can be performed with cheaper tools. Resources not spent at the integration level can be used to create additional value.

What is needed on the customer’s side?
Coming soon

Prerequisites
Coming soon

What is GUI Testing?
GUI Testing is used to avoid errors resulting from inputs that are mixed up in a form. This can be an automated GUI test, e.g. Selenium, or a manual one.

What is the expected result?
Based on the aforementioned example, checking for incorrect form filling and limiting it from the developer side will help ensure that the correct data is entered into the software.

How is it typically measured?
Unit tests based on validation scenario

When is it considered successful?
If only the right content/input is integrated into the software.

Implementation
For example Regex or other frontend validation methods

Economic view
The more secure the data entry and the more comprehensive the education of the customer is, the less chance accidental data loss or software malfunction has.

What is needed on the customer’s side?
Resources for development

Prerequisites
Validation planning

What is Beta, Stable Version Testing?
Beta, Stable Version Testing can increase customer satisfaction, that is, without it customer satisfaction can potentially decrease. For example if a non-stable software version is released or they cannot return to a stable one before users become aware of it.

What is the expected result?
Customers are already using the stable version, which is an active free UAT, version update is also safer.

How is it typically measured?
The number of bugs reported on the stable version decreases while feedback due beta/unstable anomalies as a bug report becomes less frequent.

When is it considered successful?
If customers are satisfied while using the stable version, the users of the beta version provide feedback.

Implementation
Live server duplication, version tracking

Economic view
Customer satisfaction with the stable version has increased while new upgrades become available earlier for customers who could use some development earlier.
Those using the latest version (beta) indirectly increase testing resources.

What is needed on the customer’s side?
Planning versioning
Preparing go/no-go/go-if decisions

Prerequisites
Coming soon

What is a test scenario?
A test scenario is a summary of test cases, not a specific test method. It declares testing needs, expectations and test cases while it identifies core processes and non-trivial test cases.

What is the expected result?
A document making the extent, quality, methods and aspects of the testing clear for the QA experts.

How is it typically measured?
It is typically measured with satisfaction on the QA expert’s side (with spider diagram), for example to what extent it is understandable, can be processed and reproduced, etc.

When is it considered successful?
If QA experts can perform their testing tasks without having any further questions.

Implementation
A document containing testing needs, procedures, expectations, and test cases.

Economic view
The software will be tested with the quality, content and coverage as described in the test scenario.
Test scenarios make it possible to use the resources available for testing in a self-organized and optimal way.
The testing process and content will be transparent to all project participants, both customers and suppliers.

What is needed on the customer’s side?
Knowledge of the operation of the developed software
Knowledge of test feasibility tools
Business domain knowledge

Prerequisites
Coming soon

Tech Stack

© 2023

Contact us