Now, you can avoid the hassle of capturing a screenshot, annotating the same before you finally share them with a teammate by logging onto a respective tool for creating a task. LambdaTest does it all for you.
Mark as Bug is a feature that would help you to highlight any UI observation from your test sessions on LambdaTest and share the same with your colleagues on their favourite project management/ bug tracking tools such as Jira, Trello, Hive, Paymo etc. You can choose the assignee who handles your reported task, or bug. You can even mention the description to help them understand your point better. You can do all that while testing on LambdaTest, without having to hop on to any other platform or tool.
Note: Mark as Bug feature is not restricted to any particular feature at LambdaTest. In other words, every type of testing that you perform on LambdaTest will have mark as bug embedded in it. Below are various types of testing that we offer at LambdaTest.
- Real Time Testing: To help you test your web-app with live interaction by running it on VMs hosted by LambdaTest cloud server.
- Screenshot Testing: Automated bulk screenshot testing on 25(browsers + OS) combination in a single test session.
- Responsive Testing: Perform cross browser testing across a variety of mobile & desktop devices to ensure your website renders well across different view-ports. Run resposive testing on 46 devices in a single test session.
- Automation Testing: Perform automated cross browser testing with our on-cloud Selenium Grid. You can execute parallel testing to trim down your test cycles drastically. Our Selenium Grid supports is compatible with every test automation framework that supports Selenium.
- Smart UI Testing: Automated visual regression testing that performs a pixel-to-pixel comparison between multiple images & highlights any UI deviations such as padding, icon, text, etc with respect to the baseline images.
Did You Know?
LambdaTest offers more than 2000 real browsers and browser versions on every type of testing so you could maximize test coverage of your cross browser testing.
Step 1: Visit the Automation tab from the left navigation menu to redirect yourself on the automation console. Go to AUTOMATION LOGS.
Step 2: Visiting the automation logs, you will be able to access various logs of your test script execution such as network logs, command logs, and more. By default, you would be routed to SUMMARY. In summary, you will find a button to Create Issue.
As you click on the bug icon, an integration specific form would open up. Fill the fields as per your requirement. For instance, if you have installed LambdaTest + JIRA integration then you can fill the below represented fields.
- You can select which project should the bug go under.
- You can select the assignee for that particular task.
- You can select the issue type of the bug.
- You can even post a summary to help relate the cause of the bug.
All the fields you populate, will be directly reflected in your respective project based upon the integration you have configured with your LambdaTest account. In above case, the changes would be reflect on the respective JIRA instance.
Similary, you can find the mark as bug button in EXCEPTION and COMMAND logs.
- Exception logs
- Command Logs
Got any questions?
Feel free to share them with our 24/7 chat support or you can drop a mail on [email protected] Happy testing!