marmelab / marmelab/greenframe-cli

Keywords not known

Open
#68 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
284
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Hello,

I was testing greenframe-cli with the following testing script :

```
import { test, expect } from '@playwright/test';

test('has title', async ({ page }) => {
await page.goto('https://playwright.dev/');
await expect(page).toHaveTitle(/Playwright/);
});

test('get started link', async ({ page }) => {
await page.goto('https://playwright.dev/');
await page.getByRole('link', { name: 'Get started' }).click();
await expect(page.getByRole('heading', { name: 'Installation' })).toBeVisible();
});

test('Playwright Test', async ({ page }) => {
await page.goto('https://playwright.dev/');
await expect(page).toHaveTitle(/Playwright/);
const getStarted = page.getByText('Get started');
await expect(getStarted).toHaveAttribute('href', '/docs/intro');
await getStarted.click();
await expect(page).toHaveURL(/.*intro/);
});
```

but it raised an error, since it does not recognize the test and expect keywords, even in the package.json of the greenframe-cli container the @playwright/test library.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running greenframe-cli with the Playwright script from the issue and inspect the package.json dependency context for @playwright/test. Trace how the CLI identifies test and expect keywords; done means this script is recognized and processed without the reported unknown-keyword error.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, typescript
Domain
cli, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.