In Progress
Screenshot comparison (Visual regression) - assertion step
We plan to add a separate step for screenshot comparison. The first execution will save a screenshot as a baseline, and then every next execution will be compared to this baseline screenshot. If the new screenshot is different from the baseline, the test will fail. Possibly, this step should also have an option to exclude some random elements from the DOM before taking a screenshot option to decide how this comparison should be done (pixel perfect or percentage) option to verify screenshot only for specific element on the page (given selector) Any other ideas around this feature are more than welcome.
Paweł Bylina about 2 years ago
In Progress
Screenshot comparison (Visual regression) - assertion step
We plan to add a separate step for screenshot comparison. The first execution will save a screenshot as a baseline, and then every next execution will be compared to this baseline screenshot. If the new screenshot is different from the baseline, the test will fail. Possibly, this step should also have an option to exclude some random elements from the DOM before taking a screenshot option to decide how this comparison should be done (pixel perfect or percentage) option to verify screenshot only for specific element on the page (given selector) Any other ideas around this feature are more than welcome.
Paweł Bylina about 2 years ago
Planned
Add a way to create a folder in tests page
As you create more tests it would be harder to filter and organize the scripts, would be nice if we can create a folder inside to organize it. Author: Lain H A nice feature would be the ability to group tests in the same way test steps can be grouped and the group named, expanded and collapsed. So, allow tests to be grouped, the ground named, and the individual tests expanded or collapsed in a similar fashion. A step further would be to allow a test to appear in more than one group, but I guess that’s then crossing over into Suites. Or maybe tests could be tagged and have more than one tag, and then viewed by tab with tabs expanded and collapsed? That would do 2-in-1 - grouping and allowing one test to be seen under more than one topic/slice (tag)
Rav Banaag over 2 years ago
Planned
Add a way to create a folder in tests page
As you create more tests it would be harder to filter and organize the scripts, would be nice if we can create a folder inside to organize it. Author: Lain H A nice feature would be the ability to group tests in the same way test steps can be grouped and the group named, expanded and collapsed. So, allow tests to be grouped, the ground named, and the individual tests expanded or collapsed in a similar fashion. A step further would be to allow a test to appear in more than one group, but I guess that’s then crossing over into Suites. Or maybe tests could be tagged and have more than one tag, and then viewed by tab with tabs expanded and collapsed? That would do 2-in-1 - grouping and allowing one test to be seen under more than one topic/slice (tag)
Rav Banaag over 2 years ago
Planned
Add a versioning system to allow running an old version of the test
Hey there, To integrate Bugbug into my CI/CD and have my tests pass on multiple environments, I currently have to duplicate the tests and modify the changed parts, which is inefficient... It would be great if we could have test versioning so that I could point the production-oriented test to the production environment (let's name it v1.0) and the development-oriented test (v1.1) to my development environment. With that, when I deploy dev to prod, I'll be able to point the test I've already created for dev (v1.1) directly to production. Without that, I'll have to spend time modifying the tests right after deploying dev to production, otherwise the tests would fail.
Tegomass over 2 years ago
Planned
Add a versioning system to allow running an old version of the test
Hey there, To integrate Bugbug into my CI/CD and have my tests pass on multiple environments, I currently have to duplicate the tests and modify the changed parts, which is inefficient... It would be great if we could have test versioning so that I could point the production-oriented test to the production environment (let's name it v1.0) and the development-oriented test (v1.1) to my development environment. With that, when I deploy dev to prod, I'll be able to point the test I've already created for dev (v1.1) directly to production. Without that, I'll have to spend time modifying the tests right after deploying dev to production, otherwise the tests would fail.
Tegomass over 2 years ago
Planned
Easy API testing
In some test cases, to cover scenarios, retrieving data from API is required. Today, this is something that users can achieve using a custom JS step and fetch() function, but this requires code. To simplify this process, it would be nice to add an extra step like Request API where you will be able to define a method, URL, and parameters for making requests. Using variables within this step should also be possible. Storing the response as a variable could also give a lot of flexibility to users. This could be a first step to implementing more advanced API testing for BugBug.
Paweł Bylina about 2 years ago
Planned
Easy API testing
In some test cases, to cover scenarios, retrieving data from API is required. Today, this is something that users can achieve using a custom JS step and fetch() function, but this requires code. To simplify this process, it would be nice to add an extra step like Request API where you will be able to define a method, URL, and parameters for making requests. Using variables within this step should also be possible. Storing the response as a variable could also give a lot of flexibility to users. This could be a first step to implementing more advanced API testing for BugBug.
Paweł Bylina about 2 years ago
Completed
More detailed PDF reports for test runs and suite runs
For evidentiary purposes as defined by some legal regulations (in the USA), we plan to add an option to save the results of test runs and full suite runs as a PDF with detailed information such as Step type Screenshot of the page Additional comment Step status Date of the execution The first implementation should allow users to download these reports from the UI manually. Based on the feedback, the next phase could bring some automation on how to store them without manual interactions. Any extra feature requests are welcome.
Paweł Bylina about 2 years ago
Completed
More detailed PDF reports for test runs and suite runs
For evidentiary purposes as defined by some legal regulations (in the USA), we plan to add an option to save the results of test runs and full suite runs as a PDF with detailed information such as Step type Screenshot of the page Additional comment Step status Date of the execution The first implementation should allow users to download these reports from the UI manually. Based on the feedback, the next phase could bring some automation on how to store them without manual interactions. Any extra feature requests are welcome.
Paweł Bylina about 2 years ago
In Progress
Import/Export feature for tests
BugBug does not currently have an import/export feature for tests. Exporting and importing tests can be very beneficial for users. By exporting tests, users can save their work and reuse it in other frameworks. This allows users to benefit from further advanced testing without losing their work. Users can also export multiple tests into a single file, which is compatible with many other frameworks (Selenium, Python). The export feature is especially useful to outgrow the capabilities of BugBug. In addition, users can import tests from other frameworks into BugBug (Selenium, Python). This allows users to reuse their existing test cases and test suites in BugBug. Users can also import multiple tests into BugBug at once, which saves time and effort.
Haian Abou-Karam over 2 years ago
In Progress
Import/Export feature for tests
BugBug does not currently have an import/export feature for tests. Exporting and importing tests can be very beneficial for users. By exporting tests, users can save their work and reuse it in other frameworks. This allows users to benefit from further advanced testing without losing their work. Users can also export multiple tests into a single file, which is compatible with many other frameworks (Selenium, Python). The export feature is especially useful to outgrow the capabilities of BugBug. In addition, users can import tests from other frameworks into BugBug (Selenium, Python). This allows users to reuse their existing test cases and test suites in BugBug. Users can also import multiple tests into BugBug at once, which saves time and effort.
Haian Abou-Karam over 2 years ago
Completed
Record (and run) at a specific location in a test
For me, the most time-consuming part after (and during) recording a test is the need to run the entire test from the beginning to the end (or until a certain point) if I need to change or update something. More exactly, for our longer E2E tests from start to finish they can take up to 5+ minutes, and if I need to record something at the last few groups, I need to wait minutes in a row just to reach that part in order to click or update some new elements. In the roadmap, something that would help with the above are the following two considered features: I wish that, during recording, I could "select" specific locations inside the test where the step would appear for the action I do in the recorded window. This way I could skip/ignore certain groups/components of the tests which I know are passing. Maybe something like a "Record at location" or "Change record location" button in the recording options modal, which, when pressed, would allow me to select where my action will be recorded in the test in the form of a step. If I was able to do something similar to that, I would be at least 50% faster if not more, while expanding our testsuite or even keeping it updated when needed. As mentioned, a big chunk of my time consists in waiting for a test to reach a certain point, so I can continue adding more steps. I think the best parallel I can do here is the "Record at cursor" option from Playwright: While this option is activated (and clearly marked it's on) then any action done on the webpage will be recorded I can cancel/stop/pause the option, without closing the recording window, so that I can freely navigate the webpage elements without actually recording steps. While the option is activated, I can also click any line number in the code editor where I want the step to be recorded The steps are recorded in the same manner as BugBug, from top to bottom, wherever the "cursor" is at the code line at that moment A video that captures the above behavior to get a better idea: https://streamable.com/w18bz1 In my opinion, this would be the most important feature for me while using BugBug, probably above any other improvements I can think of. 😁
Marius COJOCARIU over 2 years ago
High Priority
Completed
Record (and run) at a specific location in a test
For me, the most time-consuming part after (and during) recording a test is the need to run the entire test from the beginning to the end (or until a certain point) if I need to change or update something. More exactly, for our longer E2E tests from start to finish they can take up to 5+ minutes, and if I need to record something at the last few groups, I need to wait minutes in a row just to reach that part in order to click or update some new elements. In the roadmap, something that would help with the above are the following two considered features: I wish that, during recording, I could "select" specific locations inside the test where the step would appear for the action I do in the recorded window. This way I could skip/ignore certain groups/components of the tests which I know are passing. Maybe something like a "Record at location" or "Change record location" button in the recording options modal, which, when pressed, would allow me to select where my action will be recorded in the test in the form of a step. If I was able to do something similar to that, I would be at least 50% faster if not more, while expanding our testsuite or even keeping it updated when needed. As mentioned, a big chunk of my time consists in waiting for a test to reach a certain point, so I can continue adding more steps. I think the best parallel I can do here is the "Record at cursor" option from Playwright: While this option is activated (and clearly marked it's on) then any action done on the webpage will be recorded I can cancel/stop/pause the option, without closing the recording window, so that I can freely navigate the webpage elements without actually recording steps. While the option is activated, I can also click any line number in the code editor where I want the step to be recorded The steps are recorded in the same manner as BugBug, from top to bottom, wherever the "cursor" is at the code line at that moment A video that captures the above behavior to get a better idea: https://streamable.com/w18bz1 In my opinion, this would be the most important feature for me while using BugBug, probably above any other improvements I can think of. 😁
Marius COJOCARIU over 2 years ago
High Priority
Configure browser geolocation
Please add the functionality to configure browser geolocation to a specific coordinate/region for a test/suite. This feature would be crucial to test many apps since their behaviour might be adjusted in accordance to the geolocation, and in many cases this is a regulatory requirement of certain countries/industries.
Michał Muszyński 11 months ago
Configure browser geolocation
Please add the functionality to configure browser geolocation to a specific coordinate/region for a test/suite. This feature would be crucial to test many apps since their behaviour might be adjusted in accordance to the geolocation, and in many cases this is a regulatory requirement of certain countries/industries.
Michał Muszyński 11 months ago
Planned
Before & After steps for tests
We plan to add an option to perform some actions before test execution and (always) after test execution. This could be treated in a similar way to the setUp and tearDown functions in unit tests.
Paweł Bylina about 2 years ago
Planned
Before & After steps for tests
We plan to add an option to perform some actions before test execution and (always) after test execution. This could be treated in a similar way to the setUp and tearDown functions in unit tests.
Paweł Bylina about 2 years ago
Completed
Sorting and filtering on test suite report
It could be very useful to be able to sort every column in a test report as well as having filters to show at least the passed/failed/all tests. You can also, decouple the test code from the test name in order for that to be individually sorted as well.
Ioannis Psaronikolakis over 2 years ago
Completed
Sorting and filtering on test suite report
It could be very useful to be able to sort every column in a test report as well as having filters to show at least the passed/failed/all tests. You can also, decouple the test code from the test name in order for that to be individually sorted as well.
Ioannis Psaronikolakis over 2 years ago
Folder system for components
Folder system for components for better organization. We may use some components for a particular section of our product and some others for another section. It could be useful to have a way of distinguishing them.
Ioannis Psaronikolakis over 2 years ago
Folder system for components
Folder system for components for better organization. We may use some components for a particular section of our product and some others for another section. It could be useful to have a way of distinguishing them.
Ioannis Psaronikolakis over 2 years ago
In Progress
Support for ShadowDOM
ShadowDOM is a "new" way to handle encapsulation in web applications https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM It is also a challenge for test automation. BugBug doesn't support this technology today. We plan to add support for capturing and executing all interactions within ShadowDOM elements.
Paweł Bylina over 2 years ago
High Priority
In Progress
Support for ShadowDOM
ShadowDOM is a "new" way to handle encapsulation in web applications https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM It is also a challenge for test automation. BugBug doesn't support this technology today. We plan to add support for capturing and executing all interactions within ShadowDOM elements.
Paweł Bylina over 2 years ago
High Priority
Completed
Organization - Assign users to projects
The idea is to be able to assign members of my organization to one or multiple project. The goal is to avoid a developer that work only on the project A to have an access to project B.
Tegomass over 2 years ago
Completed
Organization - Assign users to projects
The idea is to be able to assign members of my organization to one or multiple project. The goal is to avoid a developer that work only on the project A to have an access to project B.
Tegomass over 2 years ago