🚀 NEW: Pop-up Windows Recording - [See how to test seamlessly OAuth integrations](https://docs.bugbug.io/recording-tests-steps/record-pop-up-window-actions)

Software Testing Knowledge

Professional Quality Evangelist, experienced in testing web and mobile applications.  
[linkedin.com/in/kinga-witko-b5bba659/](https://linkedin.com/in/kinga-witko-b5bba659/)

Kinga Witko

[TABLE_OF_CONTENTS]

The term “shift left” expresses movement. It can describe the movement of an entire team or individuals.
What does it do in a project or an entire development lifecycle? Putting it simply,  it reflects the position of testing on a timeline. 

**Shift Left means testing earlier in the development process.** It also means repositioning the engagement, development, and testing efforts towards the customer.


Typically, in a traditional (waterfall) model of software making, testing lands at the end of the pipeline or is one of the last phases of the process. Bringing testing at the very last stage usually causes many problems such as:

- delays in the deployment
- a lot of bugs at the end of the development lifecycle
- bugs discovered just before or after the release to production
- lack of collaboration between developers and testers through the entire process.

Poor software quality is one of the most harmful consequences of all of these pains listed above.

At first, the team members do not communicate with each other and they fail to communicate the problems early. 

It must not necessarily be a bug; sometimes there is some issue with the application setup, there is no testing environment, access to certain resources (such as specific tooling or external software providers), the task description is vague, or the team setup is incorrect. 

If communicated and fixed earlier, the entire process can be smoother and cause less frustration in the team. It also encourages people to focus more on the code quality and to deliver earlier and faster.

Most of those issues can be avoided by changing the style of working and shifting testing efforts at the beginning of the process.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-


## Agile way of working

If you care about the quality of your product, your mindset has probably shifted left already.

This approach is strongly connected with the agile way of thinking and using agile work methods in software projects.


In this setup, testing is an integrated part of the team and accelerates software development at higher quality. As a result, testers can identify bugs sooner, saving time and effort. Notably, the earlier you test, the less expensive bugs are to fix.


[T The Seven Testing Principles (ISTQB)](https://www.istqb.org/downloads/syllabi/foundation-level-syllabus.html) tell that testing everything is not possible unless a system or functionality is very simple. In practice, however,  the testing efforts should be targeted appropriately at the risk analysis, techniques, and bugs prioritization rather than be attempted thorough testing. 


One of the good methods of approaching testing strategy for a specific application can be the guideline from [Agile Testing Quadrants](https://bugbug.io/blog/software-testing/agile-testing-quadrants/). The quadrants are a taxonomy to help teams plan the testing process and testing activities and make sure they have all the resources they need to accomplish it.


## Shift Left approach and DevOps and agile background

With the rise of the DevOps movement, there is an increased focus on delivering automated, continuous improvement. It holds true for development and testing alike.

What is more, Continuous Integration (CI) and Continuous Delivery (CD) are core software development disciplines integrated into the agile software development cycle. The point is to release fully-tested and stable builds early and as often as possible. Development, delivery, and test automation are crucial components of this process. 

## What it means to “Shift Left”

As mentioned at the beginning, Shift Left testing pushes testing to the “left”, to the earlier stages in the pipeline. This improves software quality and reduces time spent on resolving issues later in the pipeline.

Introducing testing early on the “left-side” of the development process, starting with unit tests and complementing with functional and integration tests is fundamental to making CI/CD happen. But that may not be enough.

The team can go even further: to eliminate unclear and contradicting requirements and improve the end-user experience, it is best to involve test engineers in the clarifying and prioritising application requirements. Test engineers can check the available or newly created requirements or user stories for clarity, consistency, testability, and traceability.

This also improves the shift towards client happiness. An early review of the requirements and spotting the flaws marks an early start of the communication with the end-user. 

The Shift Left approach introduces more care and thought exchange concerning the client. The team can be perceived as more proactive and more dedicated to the best quality standards of a project.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-


## Benefits of Shift Left Testing for Agile and Devops teams

Agile teams benefit most from Shift Left Testing in terms of clearer specifications, smoother implementations, earlier testing, and reduced costs. However, Shift Right Testing has more benefits like the ability to incorporate user and system feedback based on real usage scenarios. 

In opposition to testing early, Shift Right can provide an additional context to the testing scenarios. Shifting right means testing at the end of the process, typically when the software is deployed to production (the post-production environment). 

It is performed by a group of experts or selected end-users. It can utilize testing methods such as API Monitoring, using Feature Toggles, or measuring the performance of a live application. 

This helps to understand the application better and discover some other flaws that could have been omitted earlier.

Nevertheless, when quality comes first:

- developers spend more time on coding because they discuss potentially good solutions - they do not investigate who pushes the code first into production without testing

- there are Unit Tests beside the application code, available and maintainable

- there is an infrastructure that allows testing before pushing to production, usually the entire team is responsible for the process health

- there is room for improvement and mistakes

- developers pair up to catch obvious errors on the fly and learn from one another

- teams estimate tasks together, taking quality and risks into account

- potential risks in the systems are spotted and minimized rather than left alone

And finally - the application is tested - not only by one automated or manual test  but by a set of different functional and non-functional scenarios. 

The tests are regularly reviewed, adjusted, and observed. This approach introduces a new way of working and highlights the value of testing.


## Benefits of the Shift-Left Testing approach

The idea of shift left testing is simple to understand but hard to implement in the development cycle. It is worth the effort though, especially when the team and the entire organization understands the main benefits of this approach, such as:

- Lower costs - as explained above, bugs detected earlier are less expensive to fix.

- Increased efficiency in the software development process.

- Improved product quality and reliability because more bugs are detected at earlier stages.

- Reduced time to market since the QA process covers the entire development cycle, not only its’ last phase.

- A competitive advantage gained by letting development teams move fast, build and defend their credibility by innovating in iterations.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-


## Get started with “Shift Left” Testing in Agile

How to approach the change and switch to early software testing? Here is the basic list: 


1. **Plan**

Shape development in a way that is friendly to Shift Left testing. Once the requirements have been established, developers and testers should ideate how to shape the coding and software testing as early as possible. 


Depending on the product expectations as well as the limitations of the team, specific strategies, such as involving testers in the project since the planning phase or using the TDD approach, might have to be crafted to accommodate the Shift Left way of working.


2.** Review the requirements**

It is best to verify not only the existing code but also all the requirements necessary for the code to be written. Early verification can spot obvious mistakes.


3. **Use Static Code Analysis**

Static code analysis is the practice of checking the code without executing it. It runs through the basic code structure and ensures that the code is aligned with many standards and guidelines. By following the approach the team can early detect:

- Programming errors

- Violations of commonly followed coding standards

- Syntax anomalies

- Security issues

A static code analysis is best done via automation. The software should scan all untested codes in a project before it moves to the test phase.

4. **Collaborate**

As in any other [agile testing](https://bugbug.io/blog/software-testing/agile-testing-organized-chaos-or-a-planned-way-of-improving-your-software/) technique - early software testing requires a lot of collaboration with the team: Developers, Product Managers, Business Analysts, and other stakeholders responsible for the overall product. 

Everybody needs to understand the value of the Shift Left approach and spot the difference after some time of the new process introduction because as a result, the client benefits from better software quality and receives a lovable product.

## Conclusion for Left Shift Testing in test automation

There are a number of benefits to left shift testing in test automation. One of the primary benefits is that it helps to identify defects earlier in the development cycle. This means that defects can be caught and addressed before they become more complex and costly to fix. In addition, left shift testing can help to reduce the overall time and effort required for testing by identifying and addressing issues earlier in the process.

Another benefit of left shift testing in test automation is that it can help to improve the quality of the software being developed. By identifying and addressing defects earlier in the process, developers can ensure that the software they are creating is of higher quality and meets the requirements of the end-users.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-


One of the keys to successful left shift testing in test automation is to incorporate testing into the development process **from the very beginning**. This means that testing is not an afterthought or an additional step at the end of the development process, but rather an integral part of the development process itself. Test automation tools and frameworks can be used to automate testing activities and make it easier to incorporate testing into the development process.

It is also important to involve testers in the development process as early as possible. This allows them to provide feedback and identify potential issues before they become more complex and difficult to fix. Testers can also work with developers to ensure that the code being developed is testable, and that the testing process is efficient and effective.

Overall, **left shift testing is an important approach in test automation that can help to improve the quality of software, reduce testing time and effort, and identify defects earlier in the development process**. By incorporating testing into the development process from the very beginning, developers and testers can work together to create software that is of higher quality and meets the needs of the end-users.

Happy (automated) testing!

large_pexels-pixabay-40716.jpg

medium_pexels-pixabay-40716.jpg

small_pexels-pixabay-40716.jpg

thumbnail_pexels-pixabay-40716.jpg

pexels-pixabay-40716.jpg

Shift Left Testing Explained

[TABLE_OF_CONTENTS]


As recent data show (https://gs.statcounter.com/browser-market-share), Chrome is the most used browser in the world, with over 64% of population stating that they use Chrome as their go-to browser.

The Chrome Developer Tools (DevTools for short) are a set of web authoring and debugging tools built into Google Chrome. The DevTools provide web developers with improved access to the internals of the browser and their web application. Did you know that they are quite useful for the Testers as well?


## Give DevTools a try in testing the web

**There are multiple functions in which Dev Tools may support your testing, not only limited to:**
- resizing (change user agents)
- screen rotation
- using Console: Debug JS – CSS, Logs
- network manipulation: Throttling, Performance
- security testing
- location change
- looking for elements (id)
- taking screenshots
- clearing cache
- test recording
- database checking (IndexedDB  - a transactional database system, like the SQL-based RDBMS)


->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## How to open Chrome Developer Tools?
To open the developer console in Google Chrome, open the Chrome Menu in the upper-right-hand corner of the browser window and select More Tools > Developer Tools.

![https://i.imgur.com/fIMFZgz.png](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/f_IMF_Zgz_bea99d61c0.png)

**You can also take shortcuts to access developer tools:**

**On Mac:** \
Command+Option+I 

**On Windows/Linux:** \
F12 or Control+Shift+ I


You can dock your DevTools window to the right of your viewport or at the bottom of the screen, depending on your preferences. By default, DevTools are docked to the right of your viewport. You can also dock to bottom, dock to left, or undock to DevTools to a separate bottom.

![https://i.imgur.com/13JgWaO.png](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/13_Jg_Wa_O_2e4ec2b59e.png)

It is possible to reorder the panels so they suit your needs best. Click and drag a panel tab to change its ordering. Your custom tab order persists across the DevTools sessions. Fun fact - if you press the ctrl+U combo, you will be able to view the source code of the webpage you are using. It will appear in a new tab so you can see every element on the page and the HTML syntax. 


->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## How to start with Chrome DevTools?
Chrome DevTools can be used in web and mobile testing. Every Tester should take advantage of it because these tools are free and easily accessible. Here is a list of the most useful ideas for testing purposes. Maybe you'll come up with new ones?

### Resizing and Rotating
It is important to check the UI of your website on mobile browsers and multiple screen resolutions. For some people, it’s “Just the UI” testing but do remember that nowadays a lion’s share of the market (54.37%) belongs to mobile browsers ([stats here](https://gs.statcounter.com/platform-market-share/desktop-mobile-tablet)). 

Moreover with the combination of command+shift+M you'll be able to use the "Toggle device" functionality. It allows you to emulate virtually any mobile device there is plus you can change the device orientation as well. 

![Browser market stats](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image7_6614995465.png)

Use the **Responsive** option in Google Chrome Developer Tools to make sure that a majority of different screen resolutions is covered.

You can select the desired resolution from the dropdown list of many different mobile devices to test against different screen sizes. DevTools tell us the screen dimensions of the device in the top menu as well. 

What is more, you are also able to rotate the screen. Screen rotation is a common cause of mobile bugs, as the mobile website layout changes when the screen is rotated, and page elements may need to reload. While it won't pretend to be the real device, it will give you a lot of hints on what other tests should be performed on your application.

![DevTools resizing and rotating](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image6_02544f7f6a.png)

### Console - debug

Either a developer or a tester can debug a website on a mobile device. 

In the **JavaScript Console** you can find all ranges of errors in the application. As the complexity of JavaScript applications increases, developers need powerful debugging tools to help quickly discover the cause of an issue and fix it efficiently. The Chrome DevTools include several useful tools to make debugging JavaScript less painful.


![DevTools console](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image9_aee0e7d98e.png)
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Network and Throttling

The **Network** option allows you to observe the workflow and load time of all elements. You are provided with insights into resources that are requested and downloaded over the network in real-time. It is of special importance in mobile testing as users expect mobile apps to work smoothly and fast.

1. Open DevTools (F12)
2. Click the ‘Network’ tab
3. Click the No Throttling dropdown
4. Select the type of connection you want to imitate
5. Reload the page to see the assets downloading at that connection speed.

The Network tab in Chrome DevTools has an option to faux throttle your network, so you can experience what your users might see visiting your website on 3G, Offline, or with your real speed connection. The **Throttling** option is also useful for visualizing how fonts are loaded. The lower the speed, the more end-user frustration on your website.

In this section, in the left upper corner, there is also a record button that allows you to preserve all the activities (logs) and compare them with other test results.

![DevTools network throttling](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image8_9e4f1f589f.png)

### Elements
The **Elements** panel allows you to see everything in one DOM tree and fosters inspection and on-the-fly editing of DOM elements. It is also a useful option for automating tests. 

**You can always access this option for a specific element on the website:**
1. Mouse-over the element (word, button, etc.)
2. Right-click on the mouse
3. Click Inspect

![DevTools Elements](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image12_3c7cc49608.png)

In the Chrome DevTools panel, you’ll be directed to the very element in the DOM structure. The Elements tab is extremely useful if you need to play around with CSS in your application. Sometimes you need to switch on and off some buttons/lists/checkboxes. It is possible in this section to select the desired elements in the DOM structure and edit them in the Styles sub-section.

There is also a handy way of locating a node element in the DOM using a CSS selector. From the elements panel, use a keyboard shortcut **(win: Ctrl+f, mac: Cmd+f)** to open up the search input UI. Enter a CSS selector into the search input UI.

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Clear Site Data
Cache clearing is one of the activities that might be used daily in the testing exercise. Chrome DevTools can successfully help you out. 

Press **Control+Shift+P or Command+Shift+P** (Mac) to open the Command Menu and then run the Clear Site Data command to clear all data related to the page, including Service workers, localStorage, sessionStorage, IndexedDB, Web SQL, Cookies, Cache, and Application Cache. 

If you don't want to delete all site data, you can control what data are deleted from **Application > Storage.**

![DevTools application storage](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image10_3278490be8.png)

### Location
This is a fantastic functionality! It shows how to test an app that must work in different locations and presents a map for you - teleportation has not been invented yet! 

There is an option in DevTools that allows you to mimic location. The option is slightly hidden:
1. Open Dev Tools
2. Click the action bar in the top right corner of the screen
3. Select More Tools
4. Click Sensors

Now you can provide a website/application with your desired geo-coordinates and pretend you are there. Remember about reloading the page with every change to the coordinates.

![DevTools location](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image11_d0b495da83.png)

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Performance Monitor

In the same **More Tools **panel you can find the Performance Monitor. Use it to get a real-time view of various aspects of a page's load or runtime performance, including:
- CPU usage.
- JavaScript heap size.
- The total number of DOM nodes, JavaScript event listeners, documents, and frames on the page.
- Layouts and style recalculations per second.

There is also a separated **Performance** tab in the upper menu, which shows the Compute Intersections in the flame chart. These options can help you to identify the events and debug on its potential performance overheads.

![DevTools Performance](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/image13_7323c216c2.png)

### Screenshots
There are two ways of taking screenshots when working with DevTools:

**Screenshots of a portion of the viewport**

1. Click **Inspect** or press Command+Shift+C (Mac) or Control+Shift+C (Windows, Linux) to enter Inspect Element Mode.
2. Hold Command (Mac) or Control (Windows, Linux) and select the portion of the viewport if which you want to take a screenshot.
3. Release the mouse. DevTools downloads a screenshot of the selected portion.

**Screenshots of specific HTML nodes**

1. Select an element in the Elements tab
2. Open the Command menu
3. Start typing node and select Capture node screenshot. DevTools downloads a screenshot of the selected node.


->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## How to Operate on Mobile Devices?

Last but not least, if you want to test the mobile option, it might be useful to know how to attach your device to Chrome DevTools.

1. Install the Chrome browser on your PC
2. Get hold of an Android smartphone
3. Find a USB cable to connect them
4. Plug your device in.
5. Type chrome://inspect in the Chrome browser.

On mobile devices, you can take advantage of Chrome Developer Tools in a very similar way to web testing. You can perform throttling, look for elements, or check the network connection. What is more, you are also able to check things in a database through Stetho (*debug bridge for Android applications*). 

If it doesn’t work right away - all you need to do is enable the developer options:
1. Open settings
2. Go to System> About phone>Version number
3. Tap on it 7 times (that’s right)

And there you go.

1. Open the developer options
2. Switch them on
3. Allow USB debugging

From now on the device should be visible in Chrome/inspect.
 
There is much more to **Chrome DevTools** - all you need is to explore the options. Each year, Chrome adds new functionalities to its extensions, including DevTools. 

The number of options expands and allows not only for better development but also better testing without multiple external tools or applications. 

For basic functional testing, Chrome DevTools is more than enough. They just require time to learn how to best use them and to benefit from all the resources they offer.


large_weevil_g22fd4954a_1280_2556da4d4e.jpg

medium_weevil_g22fd4954a_1280_2556da4d4e.jpg

small_weevil_g22fd4954a_1280_2556da4d4e.jpg

thumbnail_weevil_g22fd4954a_1280_2556da4d4e.jpg

weevil_g22fd4954a_1280_2556da4d4e.jpg

Chrome DevTools Introduction

[TABLE_OF_CONTENTS]

## Why Agile?

The word 'agile' became trendy years ago and the eagerness of using it in projects in organizations remains high even today.

We have Agile dev teams and Agile testers, Agile projects. Unfortunately, the term 'agile' has become a convenient replacement for lack of requirements, lack of documentation,  or, just basically,  a pure mess.

On the other hand, Agile means nothing more than a way of working well to reduce the cost of change and uncertainty.

## Traditional vs. Agile

Talking about methodologies is always good as it leads to spotting the difference between traditional - usually phased or gated (Waterfall) ways of making software,

![phased_or_gated](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/phased_or_gated_f4e60a9340.png)

as opposed to iterative, where every story is expanded, coded, and tested with a possible release after each iteration.

![agile.png](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/agile_4b0f766f35.png)
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## The Agile change

Agile testing influences the whole process of making software, including:
- Whole Team Approach
- Coding and testing as a single process
- Feedback, collaboration
- TDD/ATDD practices
- Test-infected developers
- Better tools
- Better designed tests 

It also allows a tester to be an actual part of the team rather than a siloed unit in an organization. A tester is not a gatekeeper or quality police but he/she provides valuable input into each phase of development.

In real life, it means that an Agile tester takes part in all team meetings, provides the input, asks questions, is invited to pair programming sessions with developers, and takes the same responsibility for the code and product as any other member of the team. Of course, it requires from the Tester a larger skill set, great communications skills, and at least basic knowledge of coding and test automation.

## How to include testing?

There are many ways for extending Test Specialist responsibilities in an Agile team. They don’t necessarily include testing itself but also include a vast range of communication, presentation, and consultation activities.

### TDD
Traditional testing relies on ample documentation. Agile testing is an approach to a process that mimics the principles of agile software development, especially where:
- Testing is done more often,
- The whole team knows how and what to test, it is possible to share tasks
- Testing relies less on documentation and more on team member collaboration.

One of the great examples of how to include testing into an agile process is to start from Test-Driven Development. The TDD methodology is a software development process that emphasizes the need for good software quality. Traditionally, a developer has written the code, and then the testing department has examined it and reported bugs. Moreover, in TDD, it is the developers who write unit tests first before even writing any code that would complete a user story.

Of course, it is possible to pair in every task, so in most situations, it is possible for a developer to work together with a Quality Expert and think of possible test cases.

The tests initially fail until the developer writes a minimal sequence of code to pass the tests. As the next step, the code is refactored to meet the quality requirements of the team.

It is possible to implement TDD into the Scrum or Kanban type of working. The point is to focus on testing and quality in general. Additionally, it makes testing more agile by moving most of the testing procedures to the early stages of the development lifecycle. When writing test scenarios at the beginning of each story, developers need to understand the requirements and cooperate with the other team members. This minimises unnecessary code creation and also resolves any doubts at the beginning of the development cycle.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Automate regression testing
Regression testing is yet another type of software testing to verify if the software, previously developed and tested, still performs correctly after changes or interface with other software. Changes may include software enhancements, patches, configuration changes, etc.

If regression testing in a software project is supposed to make any sense - it has to be performed as often as possible - at least on a sprint basis. Ideally - daily. Why? Because stable test suites would detect any unexpected system behaviors and react to a major change.

Small systems usually have checklists rather than test suites - large ones - even ‘monstrous’.
Deciding what should be automated is always tough because having automated test scripts may not be something that the team could present  to the customer. The question is rather: **WHY would you want to automate anything?**

The problem is that sometimes, automated suites are not reliable or trustworthy and the effort to keep them alive is quite hard. Test suites have to be regularly maintained and extended. Automation is great for this task but it is just another tool – not the purpose of the project.

Most importantly, even in the Agile environment, all tests need to be reviewed often and prioritized daily.

No one will benefit from extended long-running test suits. What is more, automated regression tests should be efficient and alert early in the development phase, to be of better quality and truly agile.

### Visualize testing activities
One of the great examples of working with a Scrum or Kanban board is to visualize all the tasks in the project, not only the developer’s ones.

It is a great idea for the team to select even small, repetitive manual test tasks as prospects for automation. All these ideas and tasks can be placed on a board and addressed accordingly. It doesn’t mean that a tester is responsible for doing it.

Besides, in cross-functional Agile teams, there is a great opportunity for the testers to learn more coding and test automation, and for the developers to pay more attention to code quality.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Communicate
Irrespective if a project is handled in Scrum, Kanban, or another Agile manner – the key to success is (?) the communication in the team.

Also, there are useful respective tools which help  teams deliver faster and fight for better quality and efficiency. CI/CD build tools can be easily integrated with common tools for communication such as Slack, and can inform automatically that the build is done or if the build has failed. It can also be helpful in automated regression and getting the test result accessible to everyone.

### Avoid single used solutions
The responsible software development process requires planning and adjusting, not working “here and now” and then fixing production bugs. Single–used solutions in a code, in testing, unnecessary work done in the cutting-corners mode to satisfy the customer’s demands are the things that often  boomerang in the future.

When a manager  approaches you and asks for doing development quickly instead of properly – “because it’s Agile” – remember that this is nothing else but a start of technical debt.

Discuss, propose, think, but when you agree on a shortcut – for example skipping performance testing or postponing some exploratory sessions due to lack of time – be aware of the consequences in the future.

You’ll save some time now, but you’ll be in real trouble soon.

### Explore
As Elisabeth Hendrickson said in her book “Explore it!”:

 “No matter what your job title, you most likely find yourself testing regularly. Testing is an integral part of creating anything.”

This is so true in Agile. Exploratory testing is simultaneously designing and executing tests to learn about the system, and then using your insights from the last experiment to feed the next.

Exploratory testing involves scouting around areas that the net of other forms of testing doesn’t cover. A tester interacts with the implementation, designing, and executing tiny experiments in a rapid succession.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Give and receive feedback
Every Agile Team uses feedback to improve. It does not matter whether feedback is provided daily or during longer sessions such as Retrospective or Planning. Testers are expert feedback providers, they usually have overall knowledge about the product and can advise at the beginning of brainstorming or at the end of the iteration to improve further work. Feedback lets the team make course corrections.

### Testing in Scrum
How to incorporate [testing in Scrum](https://bugbug.io/blog/software-testing/scrum-testing/)? 
The Scrum Guide doesn't say anything about testing because it's "a framework for developing, delivering, and sustaining complex products". It transcends the type of product that the team is developing, and the types of testing that the team needs to do, or how testing fits into the process is different for producing different types of software products. It does not define a specific “Tester” role, as testing is the whole team’s responsibility.

Of course, there can be a person more focused on delivering high quality, measuring application performance or assuring application security, but this role is not defined by the book. It usually means that when a team decides to work according to Scrum Guide and at the same time, there is an organizational role of a [“Software Tester”](https://bugbug.io/blog/software-testing/how-you-can-become-a-software-tester/) - an expectation might arise that this person should provide guidance for the entire team (or even organization) on how to test software most effectively and lead the others in the field.
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## Summary
It is not the choice of a methodology or technology that limits us from raising the quality of the product or including test automation in a daily routine. It is rather a drive that comes from the team and helps everybody to get better at coding, testing, and taking care of the product.

The choice of the methodology is always a process, not a single decision. It requires work and effort from every team member, not only from the tester.

If you have anything to do with test management or quality assurance - this short exercise is great for practicing on a daily basis: start your working day from a short trip around different metrics - nightly builds, code coverage, cyclomatic complexity, etc. Try to explore and add a new flavor to the testing. Every day you can make an important discovery and improve the quality of your work.



large_gran_canaria_g1792ff18b_1280_20e25d41ac.jpg

medium_gran_canaria_g1792ff18b_1280_20e25d41ac.jpg

small_gran_canaria_g1792ff18b_1280_20e25d41ac.jpg

thumbnail_gran_canaria_g1792ff18b_1280_20e25d41ac.jpg

gran_canaria_g1792ff18b_1280_20e25d41ac.jpg

Agile Testing – Organized Chaos or a Planned Way of Improving Your Software?

Reliable, modern end-to-end test automation tool that improves testers’ and developers’ work.


Before you release your product into the market, it is extremely important to properly test whether it’s functioning as intended. To do that, software developers utilize a variety of testing techniques that verify the software’s integrity. To thoroughly check their software from start to finish, developers implement **End-to-End testing**, often simply called **E2E** testing – an elaborate technique that mimics end user experience. 

There are many layers to End to End testing, as it is one of the most complex testing methods. This type of testing involves testing every part of your software that the end-user interacts with in any imaginable way.

With this guide, we want to show you the importance of E2E tests, as well as tell you precisely what they are, including a few specific examples.

**Also see:** if you're new to software automation, take a look at this [beginner's guide to automation with step-by-step screenshots](https://docs.bugbug.io/in-depth-guides/beginners-tutorial-to-automation-testing).

[TABLE_OF_CONTENTS]

## What exactly is End-to-End testing?

**End-to-End testing** is one of the most useful and informative techniques for software testing, providing valuable data about the inner workings of the program from the end-user perspective. With E2E testing, developers can thoroughly verify the behaviour of their software. During the test, you will be trying to replicate key user behaviour scenarios when using your software. The actual list of things to do varies, depending on the type of software you’re testing – but in all cases, it is rather extensive.

When performing a software testing method, like an End-to-End test on a web application, you would start with opening your browser and navigating to the proper URL, and then proceeding to use the software as intended for the end-user.

Similarly, in the case of a regular desktop application or mobile application, you would open the app just like a user would, checking out every bit of functionality that is intended for the users to work with. Keep in mind that during E2E testing you won’t need to check developer-specific aspects of the software, only the end-user perspective if it is important to you.

## End-to-End test goals

During an E2E test, your goal is to verify all of the dependencies and data integrity that directly or indirectly influence the reception of the software by the end-user. This usually includes any external services, as well as databases used by the software and metrics, as well as any other system dependencies. 

E2E tests will ideally be performed in the production environment, but this isn’t always possible. The tests can, of course, be performed in an independent End-to-End testing environment, but you should make sure it is as close to the production environment as possible.

Within the SDLC process, E2E tests are performed in the Testing phase, which is situated after Coding and before Deployment. 
->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-


## Why is End-to-End testing important?

Is End-to-End testing necessary? It is true that more and more developers make sure to implement an E2E testing phase before the final deployment of their software. There are many benefits to E2E tests, but the most crucial ones are:

- The ability to verify software performance from the end-user perspective
- Testing verifies not only the software itself but also any interrelated sub systems, increasing test coverage
- Validation of back-end systems
- Immediate end-user-like feedback on test failing

While tests such as unit testing or integration testing are very useful (functional testing), allowing you to verify the working of each component and providing quick results, they don’t give you the whole picture. By not performing E2E tests, you won’t know how the experience of using your software will look like from the end-user perspective.

For example, individual component testing (integration tests) might show promising results and full functionality. However, when combined, something goes wrong and produces a bug. By only checking individual components, you wouldn’t be able to find out about the bug. 

With a proper End-to-End test, you can verify whether everything works correctly together as it should. Even integration testing doesn’t cover all of the system components of your software, and you might never know whether every aspect of your app clicks together.

E2E testing doesn’t necessarily have to discover bugs – it can also give you useful insight into the user scenario of your product. Overall, all types of tests play their respective roles in the whole vertical end-to-end testing process (differently to horizontal end-to-end tests). Just because E2E tests give you a more complex understanding of your software as a whole doesn’t mean that other test types are less valuable. 

Before releasing your app, always make sure to proceed with a thought-through testing strategy. However, while they’re certainly extremely useful, keep in mind that E2E tests occupy the top of the testing pyramid, making them the most expensive and most difficult to perform.

End-to-End testing is also one of the few functional types of tests that can be performed manually, as well as automated - which is done especially often in Continuous Integration. In such a scenario, a chosen set of tests can be run automatically each time a new iteration is uploaded to the testing server.

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## Benefits of end-to-end testing

One of the goals of this software testing technique is to simulate the end-user's perspective. This means that this type of testing helps to verify not only the security or performance, but the business aspect as well. It will check whether the software collects and processes data as it was designed to do. End-to-end testing is essential for a comprehensive validation of your product. This testing ensures that all integrated parts of the application work together as expected.

Another purpose of E2E testing is to mitigate risks. E2E testing verifies if the software is ready for deployment. The confidence in stability is a crucial factor which the stakeholders consider while approving the next release. 

There are obviously much more obvious benefits of this form of testing (like bug fixing or testing across different user scenarios), but we described them already in this article.

## End-to-End Testing Framework

Alright, so now you know what End-to-End testing is – but how to exactly implement it? There is a wide variety of checks and individual tests that must be covered by your end-to-end testing plan, some of which include:

- Establishing test requirements in the preparation phase (including software and hardware requirements)
- Creating proper documentation
- Deciding what type of test environment will be used (production environment or independent test environment)
- Preparation of test cases and general E2E design
- Tracking of data input and output
- Test execution and evaluation

When executing E2E testing methods, developers usually follow an established E2E testing framework that guides you throughout the process, enumerating various tasks and responsibilities. The framework is relatively simple and consists of only three elements:

### Establish user functions

The User Functions relates to listing the features of your software, as well as all of its interconnected software systems. To properly measure and test software functionality, you need to first think about what you’re going to test. After you’re finished with listing user functions, remember to record everything relevant to each of them, including both the input and output data. Since E2E testing can be considered holistic, you also need to pay attention to all of the relations between every individual function – how they work together and whether there are any clashes.

### Come up with specific conditions

Now that you have established the user functions you’re going to test, you need to think about the testing conditions. Try to come up with as many quantifiable indicators that can be measured for each of the functions. These can range from response time to consistency of data flow, to simple convenience of use. Remember – you’re trying to imagine yourself as an end-user, so try to keep track of anything that might be an issue for a non-developer.

### Create individual test cases

Finally, before the E2E testing can commence, you need to prepare specific test cases for each of the conditions. At this point, you have prepared a list of user functions to test, as well as data conditions that will be measured during the test. Now, you need to create at least one test case for each of the conditions. By test cases, we mean user scenarios during which specific indicators will be able to be measured.

And by test case preparation status, we mean the precise location of the test instances being developed, as compared to intended test cases.

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## End-to-end test cases for your testing process

Congratulations, you’ve almost reached the end! At this point, you should pretty much be a walking fountain of knowledge about End-to-End tests. However, the raw theory is one thing, and implementing those types of tests for system testing in reality is another. To make the process a bit more digestible, consider this End-to-End testing example for a website with shopping functionality:

- Go to the specified URL
- Open a list of products
- Check whether the information on the list correlates with specific product pages
- Try to add the product to the cart and look for visible confirmation
- Navigate to the cart and check whether the product has been successfully added
- Double-check all of the relevant information (price, product info, etc.)
- Proceed with the check-out and verify payment options integration

See how simple it is in the end? Now you can implement E2E testing methodology in your software to ensure better end-user reception, increase your product quality, and build a positive brand image.

This is just a high level example. If you would like to learn how to create a proper test case from start to end, please check out our article on [test case creation](https://bugbug.io/blog/software-testing/how-to-write-automation-test-cases/). You will have a better understanding on how to design test cases for manual and automatic testing. Also check out our other topics in our testing guide. 

## End to End testing tools

Proper tools may play a crucial role in reducing your effort by automating your end-to-end tests. These tools provide a range of features and capabilities to support horizontal testing and vertical testing of the entire system. They allow testers to perform comprehensive testing processes. Choosing a proper tool for testing is typically a long-term investment. If you research and choose a tool that will enable you to execute and record complex user scenarios and allow testing across multiple technologies, your job will be way easier. 

One of the tools that meet such requirements is BugBug. This automated testing tool proved its efficiency for many clients. On the picture below you might see how many steps might an end-to-end scenario actually have.

![n example of a passed test with a proper output statement.](https://bugbug-homepage.s3.eu-central-1.amazonaws.com/88bc1d9e_16f8_4e1a_b33d_15e2a8d17cdf_cdfc84abfc.webp)

## Summary

End-to-end testing is a type of testing that focuses on validating the whole system from start to finish rather then testing individual functionalities. It is often seen as a software testing methodology, but it is not the case. It may be a part of a methodology (i.e. Agile testing) but it is by definition a type of software testing. 

Performing end-to-end testing covers an important task of checking data flows and focuses on testing if any functional gaps occur. This type of testing is necessary to verify if the software is ready for the next release cycle.

## Frequently Asked Questions

1. **What is automated testing?** \
Automated testing in software development is a form of software testing that uses the execution of predefined sets of operations to probe and validate the software system. The fundamental purpose of automation testing in software development is to generate objective feedback about the quality of the product. One such testing tool is Selenium. It can run UI tests. The ideal situation is to run E2E tests with both manual testing and automated testing approaches. If your application has a lot of complicated user interfaces, you'll need more end-to-end testing.

2. **What is software development lifecycle?** \
Software development lifecycle (SDLC) is the process used by developers to create, deploy and maintain software. This process includes several steps that are all closely connected with one another. These steps include requirements gathering, analysis and design, coding and testing.

3. **What is a testing pyramid?** \
In software development projects, we have limited time and resources. This is why it's important to consider our test efforts carefully and find the right balance between different types of testing. Basically, there are 3 layers in the testing pyramid: Unit Tests, Integration Tests, and E2E Tests.

3. **What is a selector?** \
A selector is a small piece of code that describes a specific button in your app. It allows you to clearly define what should be clicked in automated end-to-end tests. You can learn more about selectors using [this interactive XPath learning tool](https://bugbug.io/xpath-selector-builder/?ref=blogarticle)



Happy (automated) testing!


large_testowanie_end_to_end_98e59a7257_deae9fab1e.png

medium_testowanie_end_to_end_98e59a7257_deae9fab1e.png

small_testowanie_end_to_end_98e59a7257_deae9fab1e.png

thumbnail_testowanie_end_to_end_98e59a7257_deae9fab1e.png

testowanie_end_to_end_98e59a7257_deae9fab1e.png

What is End-to-End (E2E) Testing?

Guides to Test Automation

Software developer currently working as a tech writer and PM.  
[linkedin.com/in/marcin-%C5%82ojewski-a4191518/](https://www.linkedin.com/in/marcin-%C5%82ojewski-a4191518/)

Marcin Łojewski

small_Testing Tools for Web Application.png

thumbnail_Testing Tools for Web Application.png

Testing Tools for Web Application.png

Testing Tools for Web Application - The Ultimate Guide 2023

Testing is an ever-present part of a software developer’s job, performed at every stage of the production process. There is a wide range of test types used for software testing, some performed at various points during production, and some performed after production to confirm that the software functions as intended.

Regression testing is performed on a product that has already been finished and released. How exactly is it performed? What are the objectives and how does the procedure look? If you’re keen to find out, keep on reading as we explain everything you should know about regression testing.

[TABLE_OF_CONTENTS]

## The definition of Regression Testing

**Regression testing** is a software testing method that aims to investigate and locate any possible flaws or bugs in software that has already been fully developed. Regression Testing is performed to find out whether your software has regressed (surprise, surprise) as you continue introducing new updates and bug fixes. Whenever a piece of software is changed in any way, new bugs might emerge and some of the older ones re-emerge.

Most often, regression testing is performed immediately after introducing a new update, but it isn’t the only factor that might call for the test. If any software or hardware-related factor has changed, regression testing should be committed to find out whether everything performs as it has before the change. 

This can include any sort of bug fixes and software changes, but regression might also be caused by hardware configuration changes and electronic component degradation over time. Regression testing isn’t easy – it requires cooperation and diligence out of all of the team members, which makes it perfect for agile software development practices.

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## Regression Testing process

As with most testing efforts regression testing is an art rather than science. Let us describe the regression testing process that our development team uses. You may then use and adapt it to your existing test strategy. As regression testing is a type of testing that occurs whenever any change in your software occurs, the smartest way to start is to..

### Identify code changes

This will allow you to asses the number of test cases for regression testing that will need to be created. The testing team will need information on the impact that the current changes may have on the whole application. This is done also during this step.

### Prioritize changes

You finished step one with a list. Now you need to create a queue out of it. By proper prioritizing the changes in your software application you reduce the amount of time you will use on 

### Select for re-run

This is the part where the selection of test cases is performed. After the first test is done, test cases are categorized into reusable and obsolete ones. The reusable ones create a regression test suite. The others are will not be used for regression. 

### Categorize manual and automated regression test cases

Here is where the test automation actually begins. Test cases that occur more often within one process are perfect candidates to for the automation tool to do the work for you. If you want to automate tests in a fast and efficient way, try BugBug as your tool for regression testing. You will soon find out that it is great to reduce regression testing costs.

### Prioritize test cases

Here is where regression testing becomes a tad tricky. One would think, that the most often occurring test cases should have the biggest priority, right? Well the theory on that one is a tad different. The need for regression testing, therefor the priority, is the highest for those cases, that cover all essential features. The lowest on the other hand are stated as "technical complexities". 

### Plan and execute

This one is rather obvious, but we have to put it here. After doing all the analysis, you have to plan when regression testing is done and "push the execute button". 

## Regression Testing techniques

Regression testing can include various functional and non-functional tests in its process to thoroughly investigate the software in search of flaws. There are also many techniques with which developers and QA specialists perform regression testing, including:

- Retest All
- Regression Test Selection
- Test Case Prioritization
- Hybrid approach

### Retest All – an accurate yet expensive solution

**The Retest All ** technique is the most accurate and all-around method of regression testing, but it is also the most expensive one. In Retest All, every test case is checked again on the software to confirm if all of its parts are working as intended. That’s all there is to Retest All – it might be simple in definition, but it is definitely the hardest and most costly technique to actually perform.

### Regression Test Selection – when you realize you might not have enough for a Retest All

**Regression Test Selection** has been designed as a solution to the expensive nature of the Retest All technique. In RTS we don’t run all of the tests in our test suite, but instead we divide all of the tests into three categories – reusable test cases, retestable test cases, and obsolete test cases. In addition, RTS might actually create new test cases that haven’t been in the suite before, but might be relevant for regression tests.

If you’re interested in finding out more about regression testing examples, we recommend taking a look at Understanding Regression Testing Techniques by Gaurav Duggal and Bharti Suri. The authors further divide RTS techniques, naming two most important categories – coverage techniques and minimization techniques, and explain what are safe techniques.

**Coverage techniques** feature specific coverage criteria, often provided by the client who wants their software regression tested. These techniques sift through all test cases, selecting only the ones that are relevant for the covered parts of your software. **Minimization techniques** work in a way similar to coverage techniques, but instead of selecting cases based on set criteria, you select a minimum set of cases that you think will do the job.

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

### Test Case Prioritization – a rational approach

**Test Case Prioritization** aims to maximize the rate of fault detection, creating the most thorough regression test for the lowest cost. First you prioritize the test cases one by one. Then all of them are performed in order, starting from the most important one and finishing on the least important one. Thanks to that, even if your resources aren’t enough to perform all of the tests in your suite, you will still perform the ones that should detect the most flaws.

**TSP** might be performed in two ways – the first one, called **General Prioritization**, selects test cases that should be effective (on average) on all versions of the software you’re working with. The other way, called Version Specific **Prioritization**, only takes into account a specific version of the software, without considering other existing or potential future versions.

### Hybrid approach – the best of both worlds

When choosing one technique of regression testing is impossible – why not combine the best features of Regression Test Selection and Test Case Prioritization? 

The hybrid approach is still being developed, and every researcher gives a personal spin on the idea. Since there isn’t an exact definition of what a hybrid approach actually is, there are tons of versions available – each one with its own upsides and downsides.

## Regression Testing tools

Regression testing ensures that each version of your software runs smoothly. We have described various regression testing techniques, but our article would not be complete without a few hints of what tool to use for proper test execution. 

Regression testing is used on an incremented basis. Each release of your software means building another layer of an already high pile of multiple regression test cases. A good tool will allow you to perform regression tests without writing a single line of code. 

If you want a specific list of tools, please redirect to our article [HERE](https://bugbug.io/blog/guides/testing-tools-for-web-application/).

->[Automate your tests for free](https://app.bugbug.io/sign-up/){.markdown-cta}<-

## Disadvantages of regression testing

Well now that's a shocker isn't it? We have many articles on testing in the BugBug blog, and never have I ever wrote anything negative about testing. Until now. We found four "buts" on regression testing and we tried to tackle them immediately.

- "but regression testing is time consuming" - yes, but only if you only perform a manual test, this is why selecting a good testing tool is essential
- "but you have to do it after even the smallest patch" - yes, but this is why you build a good regression cycle. You store all the recurring tests and only build a few on top of them for that given patch. It is like CI/CD for your testing process
- "but that process might interfere with the sprint planning" - only if you do regression tests without automation. Think of it from a business perspective - would you have a task that goes cross-sprint or a large bug in the production environment?
- "but it is difficult, to write those test cases" - ah, an oldie but a goodie. There are great no-code regression testing tools. Those might be used not only by QA or other technical personnel but by a PM. Such a person would be even able to automate the test or record and recreate it. 

Regression testing is one of the key ways to have your code thoroughly checked and ready to start earning you money!

## Conclusion – is Regression Testing necessary?

As you have already learned, regression testing plays a key role in keeping the quality of your software as high as possible for as long as possible. Updates and changes to your software might introduce new problems, which is exactly why regression testing is so important – to keep user experience high throughout all iterations of your program.

Not all projects require regression testing, of course. In projects that are already finished and won’t be further updated, regression testing is mostly irrelevant. However, if you are planning to continue development further – never forget to properly regression test your software before releasing an update.


Happy (automated) testing!

large_regression_tests_blog_07c72a81f5.jpg

medium_regression_tests_blog_07c72a81f5.jpg

small_regression_tests_blog_07c72a81f5.jpg

thumbnail_regression_tests_blog_07c72a81f5.jpg

regression_tests_blog_07c72a81f5.jpg

What is Regression Testing? Everything You Need To Know

Product Updates

New Feature: Pop-Up Window Recording

Testing Tools Comparisons

Top Cypress Alternatives in 2023

Uncategorized

No-code Testing Automation: Guide to Codeless Testing and Automation Tools

Get more tips and product related content. Zero spam.

Don't miss any updates

Automate web app testing easier than ever. Without excessive costs. Faster than coding. Free forever.

End-to-end testing made simple! BugBug is a new, more intuitive tool for test automation of web apps. Get all the benefits of test automation without hiring new people or infrastructure changes.

BugBug.io | Intuitive and reliable test automation for startups

large_opengraph_image.png

medium_opengraph_image.png

small_opengraph_image.png

thumbnail_opengraph_image.png

opengraph_image.png

Features

Why Choose Us

Integrations

Book a demo

Customer Success Stories

Case studies

Create tests in your browser for free. Run the tests in the cloud for 14 days at no charge. No credit card required. 

Effortless cloud testing that fits your budget

Discover the differences of each plan and choose the offer that fits your testing needs

Industry leaders automate tests with BugBug

Frequently Asked Questions

Contact our Support Team.
They’ll give you all the information you need.

Free trial of premium features for 14 days

Automate web app testing easier than ever. Without excessive costs. Faster than coding. 

Pricing

Blog about test automation

About us

Contact

Everything you need for the entire test automation workflow

Record new tests simply by clicking in your browser. Automatically capture every click or text input. Add assertions directly while recording. Forget about writing selectors by hand; BugBug will do it for you.

Create tests without coding

Enjoy excellent performance when you run tests locally, allowing you to work more efficiently. Run tests in the cloud to regularly monitor your web application and catch bugs earlier.

Run tests in your own browser or in the cloud

Now you don't need to record your test from scratch every time you want to change it! Record new steps right in the middle of your test, just where you need it. Spend less time on manual writing of CSS or XPath Selectors.

Fix tests by re-recording

Run cloud tests every day and monitor if your app works properly. Get comprehensive notifications when a test fails. You will receive notifications with scheduled test results directly to your inbox.

Schedule test automation

Use BugBug API and Command Line Interface to run regression tests along with your CI/CD build pipelines, such as Github, Gitlab, Travis, Jenkins, or Bitbucket. Integrate with Zapier to get notifications on Slack when a test fails.

Integrate with your CI/CD pipelines

Invite your teammates to work together on test automation without time-consuming training and debates. You can involve software developers or product owners in testing within minutes.

Collaborate with your team

Unparalleled simplicity powered by unique features

Powerful features for advanced testing

You can turn test steps into "Components" that are shared across multiple tests. Maintain hundreds of tests without worrying that you will have to spend half a day fixing them. 

Edit multiple tests at once

Work in multiple environments. Create random numbers. Register users with unique email addresses. 

Use variables to handle complex tasks

You have full control over the test steps. You can update selectors, manually add advanced step types or assertions, and even custom JavaScript code.

Customise test steps with JavaScript

Need to show the results to your stakeholders? You can download a PDF report for each suite run in your project.

Generate PDF reports

Record automated tests easily for both desktop and mobile resolutions.

Build tests for mobile resolutions

See what our clients are saying

Start testing for free! No credit card required.

Test automation is too complicated. BugBug is here to make end-to-end testing ultra simple and effective. Limit your testing workload and focus on delivering great features. Without straining your budget.

Because we want you to catch bugs easier than before

Join hundreds of happy software testers that automated testing process with BugBug

We solve many problems of the test automation world

**TRULY NO-CODE SOLUTION**  
Not a tester? No problem. Our no-code BugBug test recorder will make you feel like a pro QA engineer.

**CLEAN INTERFACE**  
We are fed up with complicated testing tools. That's why we created BugBug. Our software is simple and very intuitive. No matter if you are a QA testing beginner or an experienced engineer.

Built to empower non-technical testers

**UNLIMITED FREE USERS**  
Collaborate with others when creating your test suites. Finally you can invite as many teammates as you want for free.

**UNLIMITED LOCAL TESTS**  
With BugBug you can run unlimited tests in your browser with the Free Forever Plan. Also you may run tests in the cloud without additional infrastructure or DevOps costs. Fun right?

Test automation tool that suits every pocket

**BUILT-IN AND CUSTOM VARIABLES**  
Anytime you need, you can run tests with our built-in variables that we prepared for you. If you need something more specific, you can also create your own custom variables.

**POWERFUL FEATURES**  
Run custom JavaScript, use automatic selectors, create profiles as presets for different variable values, and work with different development environments - BugBug offers advanced features for you to use when you need it.



Advanced features to boost your testing

Integrate with anything via BugBug API. Run cloud tests in your CI/CD pipelines such as Github, Travis, Jenkins, Bitbucket, or GitLab. The setup is easy thanks to BugBug's streamlined Command Line Interface and built-in Zapier support.

Are you fresh in the test automation world? We’ve got your back - read our comprehensive tutorial for beginners and see how easy it is to automate your first test.

Easy to learn testing

Read about best practices from the test automation world. Get practical tips, valuable insights, and improve your QA process.

thumbnail_eq_El_DXL_400x400_b440e8a71d.jpg

eq_El_DXL_400x400_b440e8a71d.jpg

Best Chrome Extensions for Software Testers

Scrum Testing: QA on an Agile Team 

Why is Software Testing Important?

I write about technology and help people who use it. I've always been fascinated by the details of things - how they work and what makes them tick. That's why I love writing about tech!  
[linkedin.com/in/aleksandra-spilkowska](https://linkedin.com/in/aleksandra-spilkowska)

large_a_spilkowska_cropped_c38f3487ad.jpg

medium_a_spilkowska_cropped_c38f3487ad.jpg

small_a_spilkowska_cropped_c38f3487ad.jpg

thumbnail_a_spilkowska_cropped_c38f3487ad.jpg

a_spilkowska_cropped_c38f3487ad.jpg

Aleksandra Spilkowska

Specflow: 8 Steps to Use Behavior-Driven Development To Improve Team Performance

[linkedin.com/in/darekkacban](https://linkedin.com/in/darekkacban)

thumbnail_dariusz_kacban.jpeg

dariusz_kacban.jpeg

Dariusz Kacban

Doan Nguyen - Operto - Quality Assurance Specialist

Doan Nguyen, Quality Assurance Specialist

thumbnail_Authors (1).png

Authors (1).png

Doan Nguyen

A self-taught software QA Engineer, Dominika has experience in web testing. Currently, she is focusing on developing her test automation skills with Cypress. Apart from programming, she likes to make pottery and cook vegetarian delicacies.  
[linkedin.com/in/dominikanykiel](https://linkedin.com/in/dominikanykiel)

medium_1637439945009_e_1646265600_and_v_beta_and_t_Iw_Bm_GA_Wm_Nd_Xvpr_R_Nzs_LB_Pbwu_PFXBTK_Ff_TLP_612y_Eu_A_4d4900e8b2.jpg

small_1637439945009_e_1646265600_and_v_beta_and_t_Iw_Bm_GA_Wm_Nd_Xvpr_R_Nzs_LB_Pbwu_PFXBTK_Ff_TLP_612y_Eu_A_4d4900e8b2.jpg

thumbnail_1637439945009_e_1646265600_and_v_beta_and_t_Iw_Bm_GA_Wm_Nd_Xvpr_R_Nzs_LB_Pbwu_PFXBTK_Ff_TLP_612y_Eu_A_4d4900e8b2.jpg

1637439945009_e_1646265600_and_v_beta_and_t_Iw_Bm_GA_Wm_Nd_Xvpr_R_Nzs_LB_Pbwu_PFXBTK_Ff_TLP_612y_Eu_A_4d4900e8b2.jpg

Dominika Nykiel

Unit Testing vs End-to-End Testing: Key Differences

How to Become Automated Test Engineer? 

Atomic Test Cases - the Ultimate Guide

Parallel Testing: A Guide for Software Testers

Benefits of CI/CD Pipeline Implementation

Quality Engineering vs Quality Assurance: Goals & Differences

SaaS Testing Guide: All You Need to Know

Best Selenium Practice Websites in 2023

Chaos Testing: Everything You Need To Know

Top Rainforest QA Alternatives in 2023

Top Ghost Inspector Alternatives in 2023

What is User Journey Testing? Guide for Software Testers

The Ultimate XPath Cheat Sheet

CI/CD Interview Questions and Answers

Cypress Best Practices: Test Automation Guide

Top Autify Alternatives in 2023

Top Reflect.run Alternatives in 2023

What is Performance Testing in Software Testing?

Smoke Testing vs Sanity Testing: All You Need To Know

Best Practices of Test Maintenance in Software Testing

Best Websites with Bugs for Testing

Top 15 Codeless Automation Testing Tools for QA

"What Does QA Testing Do?" in Software Development

The Landscape of Front End Testing Tools in 2023

The Ultimate Guide to Codeless Automation Testing

Best QA Conferences: Curated List for 2023 and 2024

Regression Testing in Agile: All You Need to Know

Best Software Testing Forums for QA

UI Automation Testing Tools: Curated List for QA

Front End Testing Frameworks: Explained

Functional Testing Tools: Automation Testing Guide 

Cypress Cheat Sheet: Commands, Assertions and More

New Integration: Slack x BugBug

Best Manual Testing Tools in 2023: Which One Is Right for You?

Best Automated Regression Testing Tools 

Playwright Cheat Sheet 

Selenium Cheat Sheet: Java Cheat Sheet, Commands and Locators

Testing Forms: A Comprehensive Guide for QA

Top Selenium Alternatives in 2023

Application Consultant working as a Tech Writer


[https://www.linkedin.com/in/dominikdurejko/](https://www.linkedin.com/in/dominikdurejko/)

Untitled design (25).png

Dominik Szahidewicz

Eduardo Jiménez - Aquí hay DOMINIOS - CTO, CEO, Co-Founder