What Can I Do With my Executions and 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 introduces you to the Amikoo homepage and its key features. 00:04: You'll learn how to navigate and interact with Amikoo to monitor and manage your test 00:08: executions effectively. 00:11: The homepage opens with the AmikooChat interface. You can ask Amikoo anything — for example, 00:15: typing "What 00:16: can you do?" 00:18: will switch to chat mode and return a summary of Amikoo's capabilities. 00:26: Amikoo can help with a range of tasks including understanding test coverage, 00:30: analyzing execution results, writing tests, managing your test repository, and 00:35: learning about your application. 00:37: It can work with your Amikoo QA execution history, connected GitHub repositories, 00:41: and any product knowledge files 00:43: you've provided. 00:44: If you have something specific in mind, type it directly into the prompt field to get 00:48: started right away. 00:57: Below the chat, you'll find your key test metrics. 00:59: The health score is calculated based on your pass rate and test stability. 01:04: The pass rate shows how many of your tests are currently passing, and the stability 01:08: score indicates how consistent and reliable your tests are over time. 01:12: The Recent Activity section shows your latest test runs. In this example, two tests 01:17: have been consistently failing — with failures recorded eight hours ago and again 01:21: three hours ago. 01:23: The Action Required section highlights issues that are impacting your test 01:26: reliability. 01:27: Issues are flagged as either failed or flaky. In this example, only failed tests are 01:32: present, 01:33: so no flaky tests appear. 01:35: The iterations view shows the same failing tests across different test runs. 01:40: Each run includes a video recording — if the failure had a different cause, the 01:44: video would reflect that difference. 01:49: Click through to access the video and get a more detailed breakdown of any test run 01:53: or issue. 01:55: The Today's Journey section displays your most recent test executions in sequence. 02:00: You can view up to 20 executions and scroll horizontally to browse them. 02:04: At the end of the list we have a button that takes us to the test view. 02:08: At the bottom of the homepage, suggested questions 02:10: give you quick starting points for interacting with Amikoo. 02:14: You can select one of these or type your own question directly. 02:17: This tutorial provided a comprehensive overview of the Amikoo homepage, including 02:21: the chat interface, test metrics, recent failures, action required issues, and today's 02:27: execution journey. 02:28: You can now confidently navigate the homepage and use Amikoo's features to stay on top 02:33: of your testing.

00:00: This tutorial guides you through executing tests with Amiku and receiving feedback from 00:03: those tests. 00:05: Before starting, ensure you have access to your test repository and Amiku account 00:09: credentials. 00:12: Hello. 00:12: Today we're going to learn how to execute our test with Amiku and receive the feedback 00:16: from the test we run. 00:18: So now that we've connected our test repository as well as our app repository, which 00:22: is not mandatory, we only need our tests. 00:25: We're going to be able to see the test here listed. The first time 00:29: we're not going to see the execution number since they haven't been run. 00:33: What we're going to do is go to settings and get our API key. 00:37: We'll copy it here to authenticate and receive the feedback. 00:42: We're going to go to our Visual Studio or any IDE of our preference. 00:46: We're going to need to install this npm package so we can report back to Amikoo. 00:51: Here is the minimum necessary in our Playwright config file. 00:54: Once we install, we can see it's going to report to Amiku. 01:09: Then once we've had our API key, we've saved our environment, we can go and execute 01:14: our tests. 01:16: Here we can see that all the tests have ended and it's sending an execution report. 01:21: It's uploading the videos and the execution report has been sent successfully. 01:25: So we can go back to Amiku and see our test executions. 01:30: Here we can see April 3rd to 2nd execution 01:32: number three. It was previously number two. And that's it. 01:36: That's all we need to configure our reporter to send our back to Amiku. 01:40: Remember, it's necessary to have our test repo connected and our API key. 01:46: You have successfully executed tests using Amiku, configured the necessary settings, and 01:50: reviewed the test execution history.