Execute Tests and Receive Feedback Using Amikoo

00:00: Click here to watch This tutorial 00:01: introduces you to the Test View interface and its features. 00:05: You'll learn how to navigate, filter, and analyze your tests effectively. 00:10: This tutorial covers the Test View — where you can explore, filter, and review all 00:14: the tests in your connected repository. 00:17: The Test View displays a complete list of all tests available in your test 00:21: repository. 00:23: Each test shows the status of its most recent execution. 00:25: In this example, the test passed, ran for three seconds on the main branch, and has 00:30: been executed twice. 00:32: The execution count reflects how many times a test has been run. 00:36: Each time 00:36: the test is executed, 00:37: the count increases accordingly. 00:40: The date shows when the test was most recently executed. 00:43: The Test View includes a search bar and several filters to help you quickly find 00:47: specific tests. 00:49: Use the search bar to find tests by name. For example, searching "class" or "class 00:53: manager" will return all tests with those terms in their name. 00:57: Filter your tests by status to narrow down results. 01:00: Selecting "Passed" will show only tests that have passed, hiding any failed tests from 01:04: the list. 01:06: Selecting "Failed" will display only the tests that have not passed, making it easy to 01:10: focus on what needs attention. 01:14: The stability filter shows how consistently a test passes over time. 01:17: This metric requires enough runs to calculate — make sure your tests are 01:22: executed regularly so Amikoo can determine their stability. 01:25: Select the stability filter to view tests sorted or filtered by their stability 01:29: metric. 01:31: The runtime filter lets you find tests within a specific duration range. 01:35: For example, filtering for tests above one minute will return no results 01:39: if all your tests run under a minute, while filtering for zero to one minute will display 01:43: all of them. 01:48: Refine 01:49: the runtime range as needed to find tests that fall within a specific execution 01:52: window. 01:54: Click on any test card video button to open a modal with a recording of that 01:57: execution. 01:58: This is especially useful for reviewing what happened during a failed run. 02:05: Use the execution video to investigate what went wrong and gather insights into the 02:09: cause of the failure. 02:10: Click outside the modal to close it and return to the Test View. 02:16: This tutorial walked you through the Test View in Amikoo, including how to browse your test 02:20: list, check execution statuses, apply filters, and review execution recordings. 02:25: You can now efficiently manage and analyze your tests using these features.

00:00: This tutorial helps you get started with Amikoo by walking you through your first interaction. 00:03: interaction. 00:04: Before beginning, you will need to complete the onboarding to get the most out of 00:08: Amikoo's features. 00:11: After completing onboarding, you're ready for your first interaction with Amikoo. 00:15: The chat interface displays suggested questions to help you get started 00:18: — if you're not sure where to begin, simply click on one. 00:22: Click a suggested question to explore what to focus on first in Amikoo. 00:27: For our first interaction we will ask Amikoo: "Can 00:29: you help me create tests for my application?" 00:38: Amikoo will return feedback on your application's testing setup and what's available 00:42: to work with. 00:44: Amikoo presents multiple testing scenarios tailored to your application. 00:53: Select which areas of your application you'd like to write Playwright tests for. 00:58: Begin with your application's most critical user flows to prioritize the most 01:01: important tests first. 01:05: Amikoo generates three tests ready to execute and add to your test repository for 01:10: ongoing use. 01:16: This is just one of many things you can do with Amikoo — and it's only the start of 01:20: what's possible from your very first interaction. 01:23: If you don't have a test repository connected yet, your tests won't be committed at 01:27: this stage 01:28: — that's okay. 01:29: Once a test repository is connected, you'll be able to commit your tests and open 01:33: pull requests directly from Amikoo. 01:36: This tutorial walked you through your first interaction with Amikoo, from requesting test 01:40: creation to reviewing feedback and exploring testing scenarios. 01:44: You're now ready to manage and execute tests using Amikoo's features.

00:00: This tutorial guides you through creating new tests and submitting a pull request 00:03: with a new branch. 00:05: You'll learn how to identify test coverage gaps, generate tests, and manage your 00:09: pull request from Amikoo through to GitHub. 00:13: This tutorial walks through a complete workflow: identifying coverage gaps, 00:17: generating new tests, and submitting them via a pull request on a new branch. 00:22: Ask Amikoo: "What are some gaps in my test coverage?" Amikoo will analyze your repository 00:27: and return a breakdown of untested modules. 00:30: Amikoo categorizes your coverage into three groups: areas with no tests, areas that are 00:35: partially covered, and areas that have tests but could benefit from a review. 00:40: Review the available scenarios and choose which coverage area you'd like to address 00:43: first. 00:45: In this example, an area with no existing coverage is selected, with the goal of 00:49: generating new tests and submitting them via a pull request. 00:53: Using the context from your connected repository, Amikoo creates tests for the 00:57: requested modules 00:58: — in this case, five new test files. 01:02: Amikoo displays the contents of each test file, including the test name and the 01:06: location where it will be added. 01:11: Before creating and committing the files, Amikoo presents 01:14: a full summary for your review. 01:19: The summary confirms 26 new tests across five files. Review the details before 01:24: proceeding. 01:25: The tests span several distinct areas of your application, giving you broad new 01:29: coverage in a single workflow. 01:31: Confirm to create the branch and commit the files. Amikoo creates a pull request 01:36: containing all five files and 26 tests. 01:42: Amikoo may surface warnings — for example, that the Amikoo QA reporter isn't 01:47: configured in your repository, or that no GitHub Actions workflow exists. 01:51: These are informational only and do not affect the branch or pull request creation. 01:56: Head to GitHub to view the newly created pull request. 02:01: The pull request mirrors the summary from AmikooChat — five test files with 26 new 02:06: tests covering member directory, today's schedule, instructors, analytics, and chat. 02:10: chat. 02:15: From the pull request, you can review the commits, inspect the changed files, and 02:19: merge when ready. 02:21: The pull request confirms that the branch was created by AmikooAI. 02:25: This workflow shows how quickly new tests can be created and submitted directly from 02:30: the AmikooChat interface. 02:32: Once you've reviewed the pull request, merge it to incorporate the new tests into 02:36: your main branch. 02:37: You have successfully identified coverage gaps, generated new test files, and 02:41: submitted a pull request with a new branch. 02:44: Head to GitHub to review and merge 02:46: the pull request to complete the process.