What can I do with Amikoo?

April 14 | The MuukTest Team

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.

This tutorial introduces you to the capabilities of AmikooChat. You'll learn how to create test branches, manage pull requests, and review test coverage for your application.

1. Introduction To AmikooChat

Get an overview of what you can accomplish with AmikooChat, from generating tests to managing pull requests directly through conversation.

2. Request Test Branch Creation

AmikooChat lets you target specific scenarios for testing or ask for suggestions on what to test next — making it easy to direct your coverage where it matters most.

3. Test Feature And Create Pull Request

Enter a prompt such as: "Please create a new test that covers the member detail modal in a new branch and create a PR to main." This instructs Amikoo to test a specific feature and open a pull request to your repository.

4. System Processing Actions

Amikoo will take a moment to think through the request and execute the necessary actions.

5. Summary Of Branch And Pull Request

Amikoo returns a summary of what was completed — in this case, a new branch was created, a pull request was opened, and 11 tests were added.

6. Details Of Added Tests

The tests cover a range of cases including member name, email, tier badge, join date, class name, bookings, and secondary member display. Amikoo also made decisions based on tests that already exist in your repository.

7. Avoid Duplicate Tests

Because Amikoo has the context from your connected repository, it adds only genuine new coverage and avoids duplicating existing tests.

8. System Familiarity With App

Amikoo is already familiar with your tests and application. You can go a step further and ask it directly what it knows.

9. Ask About App Knowledge

Type: "What do you know about my app?" to get a full breakdown of Amikoo's understanding of your application.

10. Await App Description

Amikoo will provide a description of your app based on the context it has gathered.

11. App Overview

In this example, Amikoo identifies the app as a gym and health club management CRM — a React application for managing memberships, class bookings, and studio operations.

12. Describe App User Roles

Amikoo can identify the roles defined in your app, such as member and admin.

13. Explain Business Rules And Testing

Amikoo surfaces your business rules, available demo data, and a summary of what has already been tested.

14. Review Test Coverage And Suggestions

The coverage overview shows what's already been tested and highlights areas that could benefit from additional test cases.

This tutorial demonstrated how to create a test branch, generate a pull request, and review test coverage using AmikooChat. You're now ready to explore more of Amikoo's testing features and manage your application's test cases with confidence.

Execute Tests and Receive Feedback Using Amikoo

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.

What Can I Do With my Executions and Amikoo?

00:00: This tutorial explains how to analyze test executions in Amikoo to identify and address 00:04: failing tests. 00:06: You'll learn how to interpret test results, review fixes, and distinguish between 00:10: product issues and test issues. 00:13: This tutorial covers what your test executions in Amikoo 00:16: can tell you and how to act on that information. 00:19: Start by asking Amikoo which tests fail most often. In this example, Amikoo identifies two 00:25: tests with a 100% failure rate. 00:30: You can ask AmikooChat to create a fix for the failing tests and open a pull request with 00:34: the changes. 00:36: Navigate to your Pull Requests on GitHub to see the actions Amikoo has taken. 00:41: The most recent pull request reflects the fix that was just requested. 00:46: The pull request includes a full breakdown of the fix — which sections were 00:50: changed, which lines were affected, and a description of what was updated. 00:56: Amikoo makes targeted edits, leaving 00:58: all unrelated tests unchanged. Only the code that needs to be fixed is touched. 01:05: Back in AmikooChat, ask: "Is there any suspicion of a product failure based on my failed executions?" 01:10: Amikoo will 01:11: analyze the results before responding. 01:22: Based on the two failing tests, Amikoo identifies two scenarios worth investigating 01:26: as potential product issues. 01:34: Amikoo differentiates between the two issues 01:36: — in one case the application itself is the likely 01:40: cause, and in the other the test is the problem. 01:47: Amikoo describes what may be causing each failure. 01:49: For example, it may flag a mismatch with an expected header value. 01:55: When a failure is harder to attribute to the test alone, Amikoo will recommend manual 01:59: verification to rule out a genuine product issue. 02:06: These examples show just two of the ways you can use test executions in Amikoo to investigate 02:11: failures and take action. 02:13: This tutorial demonstrated how to analyze test executions in Amikoo, identify failing tests, 02:18: review 02:18: fixes via pull requests, and distinguish between product and test issues. 02:24: You can now use Amikoo to confidently investigate test failures and determine when 02:28: manual checks are needed.

Create and Pull Request New Tests to Your Repo

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.