# E2E Tests

End-to-end tests that run every CLI command against real Slack and Discord APIs.

## Prerequisites

Before running E2E tests, you need:

1. **Dedicated Test Workspaces** - Create separate Slack and Discord test workspaces/servers
   - **Never run E2E tests against your business or personal accounts**
   - Tests create and delete messages, which could interfere with real work

2. **Test Channels** - Create an `e2e-test` channel in each test workspace/server
   - Slack: Channel named `e2e-test`
   - Discord: Text channel named `e2e-test`

3. **Authentication** - Either:
   - Local credentials from desktop apps (via `auth extract`)
   - Environment variables (for CI)

## Test Infrastructure

| File                      | Description                                        |
| ------------------------- | -------------------------------------------------- |
| `config.ts`               | Hardcoded test workspace/server IDs and validation |
| `helpers.ts`              | CLI runner, JSON parser, message cleanup utilities |
| `slack.e2e.test.ts`       | Slack command tests                                |
| `slackbot.e2e.test.ts`    | SlackBot command tests                             |
| `discord.e2e.test.ts`     | Discord command tests                              |
| `discordbot.e2e.test.ts`  | DiscordBot command tests                           |
| `teams.e2e.test.ts`       | Teams command tests                                |
| `webex.e2e.test.ts`       | Webex command tests                                |
| `telegram.e2e.test.ts`    | Telegram command tests                             |
| `whatsapp.e2e.test.ts`    | WhatsApp command tests                             |
| `whatsappbot.e2e.test.ts` | WhatsApp Bot command tests                         |
| `line.e2e.test.ts`        | LINE command tests                                 |
| `instagram.e2e.test.ts`   | Instagram command tests                            |
| `kakaotalk.e2e.test.ts`   | KakaoTalk command tests                            |
| `channeltalk.e2e.test.ts` | Channel Talk command tests                         |
| `channeltalkbot.e2e.test.ts` | Channel Talk Bot command tests                  |

## Running E2E Tests Locally

### Step 1: Authenticate

First, make sure the desktop apps (Slack/Discord) are running and logged into your **test** workspaces.

```bash
# Extract Slack credentials
agent-slack auth extract

# Extract Discord credentials
agent-discord auth extract

# Extract Teams credentials
agent-teams auth extract
```

> For local runs you can also use QR code sign-in for the **test** accounts (`agent-slack auth qr` / `agent-discord auth qr`) instead of extraction — it's the recommended auth method and doesn't require the desktop app. CI uses the environment variables below (extracted token/cookie values), since QR sign-in is interactive.

### Step 2: Switch to Test Workspace

Ensure you're targeting the correct test workspace:

```bash
# Verify Slack workspace
agent-slack workspace current
# Should show: "Agent Messenger" (T0AC55BSF6E)

# Verify Discord server
agent-discord server current
# Should show: "Agent Messenger" (1467039439770357844)
```

If wrong, switch workspaces:

```bash
agent-slack workspace switch <test-workspace-id>
agent-discord server switch <test-server-id>
```

### Step 3: Run Tests

```bash
# Run all E2E tests
bun test e2e/

# Run only Slack tests
bun test e2e/slack.e2e.test.ts

# Run only SlackBot tests
bun test e2e/slackbot.e2e.test.ts

# Run only Discord tests
bun test e2e/discord.e2e.test.ts

# Run only Teams tests
E2E_TEAMS_TEAM_ID=<id> E2E_TEAMS_CHANNEL_ID=<id> bun test e2e/teams.e2e.test.ts

# Run specific test by name
bun test e2e/slack.e2e.test.ts --test-name-pattern "message send"
```

## Running E2E Tests in CI (GitHub Actions)

### Required Secrets

Set these secrets in your GitHub repository settings:

#### Slack Secrets

| Secret                     | Description                 | How to Get                                |
| -------------------------- | --------------------------- | ----------------------------------------- |
| `E2E_SLACK_TOKEN`          | Slack auth token (xoxc-...) | `agent-slack auth extract` → check output |
| `E2E_SLACK_COOKIE`         | Slack cookie (xoxd-...)     | Same as above                             |
| `E2E_SLACK_WORKSPACE_ID`   | Test workspace ID           | `agent-slack workspace current`           |
| `E2E_SLACK_WORKSPACE_NAME` | Test workspace name         | Same as above                             |

#### Discord Secrets

| Secret                  | Description        | How to Get                                  |
| ----------------------- | ------------------ | ------------------------------------------- |
| `E2E_DISCORD_TOKEN`     | Discord auth token | `agent-discord auth extract` → check output |
| `E2E_DISCORD_SERVER_ID` | Test server ID     | `agent-discord server current`              |

#### Teams Secrets

| Secret                 | Description                       | How to Get                                |
| ---------------------- | --------------------------------- | ----------------------------------------- |
| `E2E_TEAMS_TOKEN`      | Teams auth token (skypetoken_asm) | `agent-teams auth extract` → check output |
| `E2E_TEAMS_TEAM_ID`    | Test team ID                      | `agent-teams team list`                   |
| `E2E_TEAMS_CHANNEL_ID` | Test channel ID                   | `agent-teams channel list`                |
| `E2E_TEAMS_TEAM_NAME`  | Test team name (optional)         | `agent-teams team current`                |

### Getting Credentials for CI

Run locally to extract credentials, then copy them to GitHub Secrets:

```bash
# Slack - extract and view credentials
agent-slack auth extract
cat ~/.agent-messenger/slack/credentials.json
# Copy token and cookie values

# Discord - extract and view credentials
agent-discord auth extract
cat ~/.agent-messenger/discord/credentials.json
# Copy token value
```

### Workflow Triggers

The E2E workflow (`.github/workflows/e2e.yml`) runs:

- **Manually**: Via `workflow_dispatch` (Actions tab → Run workflow)
- **On PRs**: When changes are made to `src/`, `e2e/`, or `package.json`

### Manual Trigger Options

When triggering manually, you can select which platform to test:

- `all` - Run both Slack and Discord tests (default)
- `slack` - Run only Slack tests
- `discord` - Run only Discord tests

## Test Coverage

### Slack Tests

| Command Group | Tests                                                          |
| ------------- | -------------------------------------------------------------- |
| `auth`        | status                                                         |
| `workspace`   | list, current                                                  |
| `message`     | send, list, get, edit, delete, thread reply, replies, search |
| `channel`     | list, list --type, info, history                               |
| `user`        | list, me, info                                                 |
| `reaction`    | add, list, remove                                              |
| `file`        | upload, list                                                   |
| `unread`      | counts, mark                                                   |
| `activity`    | list                                                           |
| `saved`       | list                                                           |
| `drafts`      | list                                                           |
| `sections`    | list                                                           |
| `snapshot`    | default, --channels-only, --users-only                         |

### SlackBot Tests

| Command Group | Tests                                                  |
| ------------- | ------------------------------------------------------ |
| `auth`        | status                                                 |
| `message`     | send, list, get, edit, delete, thread reply, replies |
| `channel`     | list, info                                             |
| `user`        | list, info                                             |
| `reaction`    | add, remove                                            |

### Discord Tests

| Command Group | Tests                                      |
| ------------- | ------------------------------------------ |
| `auth`        | status                                     |
| `server`      | list, current, info                        |
| `message`     | send, list, get, delete, ack, search       |
| `channel`     | list, info, history                        |
| `user`        | list\*, me, info                           |
| `reaction`    | add, list, remove                           |
| `file`        | upload, list, info                         |
| `snapshot`    | default\*, --channels-only, --users-only\* |

\* Some Discord tests are skipped because they require Bot Token permissions not available to user tokens.

### Teams Tests

| Command Group | Tests                                  |
| ------------- | -------------------------------------- |
| `auth`        | status                                 |
| `team`        | list, current, info                    |
| `message`     | send, list, get, delete                |
| `channel`     | list, info, history                    |
| `user`        | list, me, info                         |
| `reaction`    | add, list, remove                      |
| `file`        | upload, list, info                     |
| `snapshot`    | default, --channels-only, --users-only |

> ⚠️ Teams tests require `E2E_TEAMS_TEAM_ID` and `E2E_TEAMS_CHANNEL_ID` environment variables. Teams tokens expire in 60-90 minutes.

### DiscordBot Tests

| Command Group | Tests                                            |
| ------------- | ------------------------------------------------ |
| `auth`        | status                                           |
| `message`     | send, list, get, edit, delete, thread, replies |
| `channel`     | list, info                                       |
| `user`        | list, info                                       |
| `reaction`    | add, remove                                      |
| `server`      | list, current                                    |

### Webex Tests

| Command Group | Tests                                        |
| ------------- | -------------------------------------------- |
| `auth`        | status                                       |
| `message`     | send, list, get, delete, edit                |
| `space`       | list, info                                   |
| `member`      | list                                         |
| `snapshot`    | default, --spaces-only, --members-only       |

> ⚠️ Webex tests require `E2E_WEBEX_SPACE_ID`. Optionally set `E2E_WEBEX_DM_EMAIL` for DM tests.

### Telegram Tests

| Command Group | Tests                |
| ------------- | -------------------- |
| `auth`        | status, list         |
| `chat`        | list, search, get    |
| `message`     | send, list           |

> ⚠️ Telegram tests require `E2E_TELEGRAM_CHAT_ID`.

### WhatsApp Tests

| Command Group | Tests                |
| ------------- | -------------------- |
| `auth`        | status, list         |
| `chat`        | list, search         |
| `message`     | send, list, react    |

> ⚠️ WhatsApp tests require `E2E_WHATSAPP_CHAT_ID`.

### WhatsApp Bot Tests

| Command Group | Tests                |
| ------------- | -------------------- |
| `auth`        | status, list         |
| `message`     | send                 |
| `template`    | list, get            |

> ⚠️ WhatsApp Bot tests require `E2E_WHATSAPPBOT_PHONE_NUMBER`.

### LINE Tests

| Command Group | Tests                |
| ------------- | -------------------- |
| `auth`        | status, list         |
| `chat`        | list                 |
| `friend`      | list                 |
| `message`     | send, list           |
| `profile`     | (top-level command)  |

> ⚠️ LINE tests require `E2E_LINE_CHAT_ID`.

### Instagram Tests

| Command Group | Tests                                   |
| ------------- | --------------------------------------- |
| `auth`        | status, list                            |
| `chat`        | list, search                            |
| `message`     | send, list, send-to\*, search, search-users |

\* `message send-to` requires `E2E_INSTAGRAM_USERNAME` to be set.

> ⚠️ Instagram tests require `E2E_INSTAGRAM_THREAD_ID`. Optionally set `E2E_INSTAGRAM_USERNAME` for send-to tests.

### KakaoTalk Tests

| Command Group | Tests                |
| ------------- | -------------------- |
| `auth`        | status, list         |
| `chat`        | list, list --search  |
| `message`     | send, list           |

> ⚠️ KakaoTalk tests require `E2E_KAKAOTALK_CHAT_ID`.

### Channel Talk Tests

| Command Group | Tests                             |
| ------------- | --------------------------------- |
| `auth`        | status, list                      |
| `group`       | list, get, messages               |
| `message`     | send, list, get                   |
| `chat`        | list                              |
| `manager`     | list                              |
| `bot`         | list                              |
| `snapshot`    | default                           |

> ⚠️ Channel Talk tests require `E2E_CHANNEL_WORKSPACE_ID`.

### Channel Talk Bot Tests

| Command Group | Tests                             |
| ------------- | --------------------------------- |
| `auth`        | status                            |
| `group`       | list, get (by id), get (by @name), messages |
| `message`     | send, list, get                   |
| `manager`     | list, get                         |
| `bot`         | list                              |
| `snapshot`    | default                           |

> ⚠️ Channel Talk Bot tests require `E2E_CHANNELTALKBOT_WORKSPACE_ID` (legacy `E2E_CHANNELBOT_WORKSPACE_ID` still accepted as fallback).

## Troubleshooting

### "Wrong workspace" / "Wrong server" Error

The tests detected you're not in the designated test workspace:

```
Error: Wrong Slack workspace. Expected: Agent Messenger (T0AC55BSF6E), Got: My Company (TXXXXXX)
```

**Solution**: Switch to the correct test workspace before running tests.

### Authentication Failed

```
Error: Slack authentication failed. Please run: agent-messenger slack auth login
```

**Solution**:

1. Make sure the desktop app is running
2. Run `agent-slack auth extract` or `agent-discord auth extract`
3. For CI, check that secrets are correctly configured

### Rate Limiting

If tests fail intermittently with rate limit errors, try running fewer tests at once:

```bash
bun test e2e/slack.e2e.test.ts --test-name-pattern "auth"
```

The test harness includes automatic delays between API calls, but heavy testing may still hit limits.

### Orphaned Test Messages

If tests crash before cleanup, you may have leftover messages in the `e2e-test` channel. Clean them up manually:

```bash
# List recent messages
agent-slack message list e2e-test --limit 20 --pretty

# Delete specific message
agent-slack message delete e2e-test <ts> --force
```

### CI Environment Variables Not Working

Verify the credential managers are reading env vars:

```bash
# Test locally with env vars
E2E_SLACK_TOKEN=xoxc-test E2E_SLACK_COOKIE=xoxd-test bun -e "
  import { CredentialManager } from './src/platforms/slack/credential-manager.ts';
  const cm = new CredentialManager();
  const creds = await cm.getWorkspace();
  console.log(creds);
"
```

If this shows your test credentials, env var support is working.

## Safety Features

1. **Hardcoded Test IDs**: Test workspace/server IDs are hardcoded in `config.ts`. Tests will refuse to run against other workspaces.

2. **Environment Validation**: Before any write operations, tests call `validateSlackEnvironment()` or `validateDiscordEnvironment()` to verify the correct workspace.

3. **Automatic Cleanup**: Tests track created messages and delete them in `afterEach` hooks.

4. **Rate Limiting**: Built-in delays between API calls prevent hitting rate limits.

## Adding New Tests

1. Follow existing patterns in `slack.e2e.test.ts` or `discord.e2e.test.ts`
2. Use helpers from `helpers.ts` for CLI execution
3. Track created resources for cleanup in `afterEach`
4. Add appropriate delays with `waitForRateLimit()`

Example:

```typescript
test('my new test', async () => {
  const testId = generateTestId()
  const { id } = await createTestMessage('slack', SLACK_TEST_CHANNEL_ID, `Test ${testId}`)
  testMessages.push(id) // Track for cleanup

  await waitForRateLimit()

  // Your test assertions here
  const result = await runCLI('slack', ['some', 'command', id])
  expect(result.exitCode).toBe(0)
})
```