# Tags

### Targetting Test with Tags <a href="#targetting-test-with-tags" id="targetting-test-with-tags"></a>

Let say I have now several features like the two examples below: `my-first-feature.feature`

```
@core
Feature: My Feature
	As Autokin tester
	I want to verify that all API are working as they should

Scenario: My First Scenario
    Given that a secure endpoint is up at reqres.in
    When I GET /api/users/2
```

The above feature file we tag that as `@core` feature, while below we tag that as `@fix-321` to denote that this is for the fix for 321 issue.

`my-second-feature.feature`

```
@fix-321
Feature: My Feature
	As Autokin tester
	I want to verify that all API are working as they should

Scenario: Verify if API does not accept character id
    Given that a secure endpoint is up at reqres.in
    When I GET /api/users/abc
```

So now we want to run the test but only focus on running `@fix-321`. WE can do this by using the following command.

```
./node_modules/.bin/autokin -e -t @fix-321
```

If we want to run only `@core` then we can use the following:

```
./node_modules/.bin/autokin -e -t @core
```

If we are not passing the tags `-t` or `--tags` parameter, it will run everything.

### &#x20;<a href="#tags-for-exceptions" id="tags-for-exceptions"></a>

### Tags for exceptions <a href="#tags-for-exceptions" id="tags-for-exceptions"></a>

What if we want to run everything but not the @core, then we can also use the following command:

```
./node_modules/.bin/autokin -e -t "not @core"
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://autokin.gitbook.io/docs/features/tags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.