The cypress-example-circleci-orb from cypress-io

Start iterating with inline orb

You can make an inline orb like this https://github.com/CircleCI-Public/config-preview-sdk/blob/master/docs/orbs-authoring.md#getting-started-template

Test executor pass

for example use Chrome browser for testing

cypress-io/circleci-orb#20

A way to conditionally record tests

At the moment there's no way to conditionally record the tests.

The only way to trigger recording is by hardcoding the record: true in the Orb declaration.

In our case, we want to record tests on staging branch only.

Is there any way to achieve this?

I noticed multiple people have the same issue eg: https://discuss.circleci.com/t/cast-an-environment-variable-to-a-boolean/37867/2https://github.com/cypress-io/cypress-example-circleci-orb/issues/2

Rename this repo

Should go from:

https://github.com/cypress-io/circleci-orb-test

...to...

https://github.com/cypress-io/example-circleci-orb

This will match all of our other example repos correctly.

Add "build" command

and show how to use Cypress orb to run it

Update Dependencies (Renovate Bot)

This master issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.

chore(deps): update dependency ava to version 1.4.1 🌟
chore(deps): update dependency mocha to version 6.1.4 🌟
chore(deps): update dependency ts-node to version 8.1.0 🌟

Rate Limited

These updates are currently rate limited. Click on a checkbox below to override.

Test cypress base-10 executor

because there is a report that it is not available cypress-io/circleci-orb#34 (comment)

Add example with starting the server

From cypress-io/circleci-orb#6

Dependency Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Repository problems

These problems occurred while renovating this repository.

WARN: Found renovate config warnings

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

chore(deps): update dependency ajv to version 6.12.3 🌟
chore(deps): update dependency moment to version 2.29.2 🌟
chore(deps): update dependency execa to version 4.1.0 🌟
chore(deps): update dependency mocha to version 6.2.3 🌟
chore(deps): update dependency mocha to version 7.2.0 🌟
chore(deps): update dependency ts-node to version 8.10.2 🌟
Click on this checkbox to rebase all open PRs at once

Check this box to trigger a request for Renovate to run again on this repository

Add command to run all tests in parallel

Need a command to check out code, install dependencies and run all tests in parallel

Specify Node version used for dev of repo

Can you note the Node version required to run this repo in dev? Either in package.json engines or a .node-version file?

Oftentimes I use to set node version during dev, but also to determine whether to merge in PRs from packages that remove node version support.

How to pass conditional --record CLI flag

based on record parameter?
and it would be nice to check if the environment variable CYPRESS_RECORD_KEY is present too maybe

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

nomenclature of job names, parameters, etc

https://github.com/cypress-io/circleci-orb-test/blob/0314523f0bbff82d4242b80d8371f08544bcd878/.circleci/config.yml#L8

Instead of:

runner/e2e

Could have:

runner/run

This would bring it better into parity with cypress run.

We could also rename the orb to be cypress/cypress as you originally had it.

Then it would be:

cypress/run

Which is the closest to what we have.

I'm trying to think if we have any other "commands/jobs/whatever" besides run. If we did exposed other things like caching or whatever then it would make sense - but those all would likely parameters of the job right?

What about handling things like browsers? Is that just another option to cypress/run?

cypress/run:
	browsers: 'whatever'
	node: 10
	record: true
	group: me

Edit:

I know that this is super premature, but if we did release like a Cypress runner for just node (and not browser testing) - what would it be called?

Would it be better to namespace like this: cypress/browser vs cypress/node or something like cypress/cypress and then cypress/node with its own job name like: node/run

Edit 2:

Should we separate out the jobs into smaller pieces? Like cypress/install or cypress/cache or whatever?

If we did the install job then users could use it independently from the cypress/run and likely better cache, etc by doing that job first, and then running cypress/run later. Since cypress/run would already check to see if its installed it should "just work". cypress/install would be optional though.

cypress-io / cypress-example-circleci-orb Goto Github PK

cypress-example-circleci-orb's People

Stargazers

Watchers

Forkers

cypress-example-circleci-orb's Issues

Awaiting Schedule

Rate Limited

Repository problems

Rate Limited

Open

Recommend Projects

Recommend Topics

Recommend Org