Paweł Bylina

Team

Created Full-page visual screenshot Created Accessibility Check Step (axe-core)Commented on Black-listing elements (internal adblock)Got it, we started working on this one Commented on Projects list: new view with details and sortingShipped!Created Parallel run limits per organization, suite and manual execution Commented on Profile for new suites / testsShipped!Created Automatic Network Error Detection Created Profile for new suites / tests Created Projects list: new view with details and sorting Commented on Store tests as scripts in the git repository@Kristian Nissen export/import shipped https://docs.bugbug.io/export-import-and-backup/exporting Commented on Summary report generation for test&suite runsAn extra requirement: Data export (CSV/JSON) Run-level counting - totals should count individual runs, not distinct tests. The current wording ("total number of executed tests") is ambiguous; for a test scheduled every 5 minutes, the customer expects ~288 runs/day, not "1 test".…Commented on Vercel integrationShipped! https://docs.bugbug.io/integrations/vercel Created Blocking tests in suites (skip the rest when a prerequisite fails)Created Option to disable test globally from every suite Created Vercel integration Commented on Import/Export feature for testshttps://docs.bugbug.io/export-import-and-backup/import-export Commented on Dashboard for scheduled testsThis has been implemented some time ago on the test and suite level. Any feedback more than welcome.Commented on Expose network logs (HAR) as a downloadable artifact in the REST APIShipped!Commented on Bugbug Folders - Improvement suggestions“An easy way to see the nested folders without having to open the main folder. Hilight also which folders have nested items.” This is why you have this option - to show every test within the full path Commented on Bugbug Folders - Improvement suggestionsYes, but what do you expect then?Commented on Add a way to create a folder in tests pageThanks!Commented on Ability to see edit history of a test and revert specific changes in test@Amanda Edgerton thanks for your feedback! We plan to add this within this feature request https://feedback.bugbug.io/p/add-a-versioning-system-to-allow-running-an-old-version but this is a separate use case so I approve it :)Commented on Add a way to create a folder in tests pageI’m excited too!Commented on BugBug-MCP / Integrate AI to write tests based on a promptFor sure for paid plans, but we don’t know yet.Commented on Extent variables with failed step id/name, and failure message/error@Filip Szwedo shipped! https://docs.bugbug.io/collaboration/alerts/sending-webhook#:~:text=%7D%2C-,%22failedStep%22,-%3A%20%7B Commented on Assert the element has an attribute with specific value@Daniel Moreno we will add it. Today, you can use Custom JavaScript for this. If you need help support@bugbug.io can create it for you.Commented on Extent variables with failed step id/name, and failure message/errorThis is the new structure and we will add those two fields to it https://docs.bugbug.io/collaboration/alerts/sending-webhook Created LLM assertion for text Created BugBug-MCP / Integrate AI to write tests based on a prompt Commented on Extent variables with failed step id/name, and failure message/error@Filip Szwedo Sorry for my late reply. I’ve missed this feature request. Would a combination of failed stepId and errorCode be enough? For example: stepId: a048f587-1c33-4bd1-88b3-ec9157014e48 errorCode: ELEMENT_DOES_NOT_EXIST