Amikoo Home Overview

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 introduces you to the capabilities of AmikooChat. You'll learn how to create 00:04: test branches, manage pull requests, and review test coverage for your application. 00:08: application. 00:10: Get an overview of what you can accomplish with AmikooChat, from generating tests to managing 00:14: pull requests directly through conversation. 00:18: AmikooChat lets you target specific scenarios for testing or ask for suggestions on what 00:22: to test next — making it easy to direct your coverage where it matters 00:25: most. 00:29: Enter a prompt such as: "Please 00:31: create a new test that covers the member detail modal in a new branch and create a 00:35: PR to main." 00:38: This instructs Amikoo to test a specific feature and open a pull request to your repository. 00:42: Repository. 00:43: Amikoo will take a moment to think through the request and execute the necessary 00:47: actions. 00:48: Amikoo returns a summary of what was completed 00:50: — in this case, a new branch was 00:53: created, a pull request was opened, and 11 tests were added. 00:57: The tests cover a range of cases including member name, email, tier badge, join date, 01:02: class name, bookings, and secondary member display. 01:05: Amikoo also made decisions based on tests that already exist in your repository. 01:11: Because Amikoo has the context from your connected repository, 01:14: it adds only genuine new coverage and avoids duplicating existing tests. 01:19: Amikoo is already familiar with your tests and application. 01:22: You can go a step further and ask it directly what it knows. 01:27: Type: 01:27: "What do you know about my app?" to get a full breakdown of Amikoo's understanding of 01:32: your application. 01:33: Amikoo will provide a description of your app based on the context 01:36: it has gathered. 01:39: In this example, Amikoo identifies the app as a gym and health club management CRM — 01:44: a React application for managing memberships, class bookings, and studio operations. 01:49: Amikoo can identify the roles defined in your app, such as member and admin. 01:54: Amikoo surfaces your business rules, available demo data, and a summary of what has 01:59: already been tested. 02:01: The coverage overview shows what's already been tested and highlights areas that could 02:05: benefit from additional test cases. 02:08: This tutorial demonstrated how to create a test branch, generate a pull request, and 02:13: review test coverage using AmikooChat. You're now 02:15: ready to explore more of Amikoo's testing features and manage your application's test 02:19: cases 02:20: with confidence.