cypress-io/cypress-example-conduit-app

[ARCHIVED] Conduit example blogging app.

🚩 Looking for another real-world demonstration of Cypress in action? Check out the Cypress Real World App repository.

Conduit App

Fork of applitools/cypress-applitools-webinar which is a fork of gothinkster/realworld "Conduit" blogging application.

Tests

The tests are in cypress/integration folder

• feeds-spec.js shows how to check the favorite articles feed and the global feed
• follow-user-spec.js shows how to create two users and check if one user can follow the other
• login-spec.js checks if the user can log in via UI and via API
• new-post-spec.js verifies that a new article can be published and updated
• profile-spec.js lets the user edit their profile
• register-spec.js tests if a new user can register
• tags-spec.js checks if tags work
• pagination-spec.js creates many articles via API calls and then checks if they are displayed across two pages
• force-logout-spec.js verifies that unauthorized API calls force the user session to finish

Full code coverage

Front- and back-end coverage for this application is collected using the @cypress/code-coverage plugin. You can run the locally instrumented server and client using npm run dev:coverage command. The backend coverage is exposed in server/server/index.js via endpoint listed in cypress.json (usually GET /__coverage). The frontend coverage is collected by instrumenting the web application source code on the fly, see the client/.babelrc file.

The combined report is saved in coverage/index.html after the tests finish:

The coverage is sent to Coveralls.io using command npm run coveralls from CircleCI AFTER partial coverage information from parallel E2E test runs is combined, see circle.yml file.

Combining code coverage from parallel runs

If you do not use an external code coverage service for combining code coverage reports, you need to combine those reports yourself like this repository is showing in circle.yml file. Several E2E cypress/run jobs run in parallel, each job saving its own coverage report folder. Then every job copies the report (using save-partial-coverage-report command) into a unique folder to avoid overwriting via reports from other machines. When all E2E jobs are finished, and reports are copied together, then the CI calls a command to merge the reports (see the merge-coverage-reports command that uses nyc merge tool).

To learn more, read the Cypress code coverage guide.

Requires Python 2.7 for node-gyp to be compiled.

cypress-example-conduit-app's Issues

Server fails to start with `npm start`

Example Job: https://app.circleci.com/pipelines/github/cypress-io/cypress/27277/workflows/6f462287-b7fd-4644-9582-5862fa1affa0/jobs/1029540

Other Notes

This repo is used to test the cypress binary release. The test has been disabled due to the server failing to run. Once this is fixed, we need to re-enable the test-binary-against-conduit-chrome job in the linux workflow in the cypress cirlceci configuration.

Dependency Dashboard

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

Open

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

• chore(deps): lock file maintenance

---

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

Potential error in merging code coverage

While trying to split some specs in PR

I have noticed that the coverage fell but then went back up without any code changes. Compare

Coverage 93.95% run https://circleci.com/gh/cypress-io/cypress-example-realworld/374#artifacts/containers/0 report https://374-193011024-gh.circle-artifacts.com/0/root/project/coverage/lcov-report/index.html

and then next run with exactly the same specs

Coverage 95.2% build https://377-193011024-gh.circle-artifacts.com/0/root/project/coverage/lcov-report/index.html report https://circleci.com/gh/cypress-io/cypress-example-realworld/377#artifacts/containers/0

Hmm, maybe the merge does not merge files if they are not created? Maybe related to #54

Code coverage service is not responding

Maybe repo rename?

Only renovate a few of our dependencies

No need to be upgrading every dependency, just ours

https://glebbahmutov.com/blog/whitelist-renovate/

Update to work on Node 12

Since Cypress v3.5.0+ is using Node 12 and FF executor runs on Node12

simplify code coverage merge

Probably use custom CircleCI commands

Need help for server request error.

hello,
I've cloned this repo & installed all the dependencies on the client, server directories. For running servers, I run commands npm start in both client & server. But whenever I'm running any cypress tests or doing signup/login in http://localhost:4100/. I'm getting this error: Debug: request, error, close on the server directory. Both servers http://localhost:3000, http://localhost:4100/ ran during the test & Please also see the screenshot for better understanding. Do I have to do any other steps or tasks for the server to works? Also, do I need to do any database setup/configuration for this?
Thanks in advance.

add get by data-cy command

Because we use data-cy attributes in our tests, let's avoid verbose tests by adding a custom command

Split new post spec: too long, and tests different features

The single spec dominates the test run

Add tsconfig or jsconfig to have intellisense for custom commands

We have a couple of extra commands in https://github.com/cypress-io/cypress-example-realworld/blob/master/cypress/support/index.js and it would be nice to have them in intellisense

Show how to test duplicate article title support

In file /server/lib/models/article.js we have a missed branch that creates a slug for an article - if there is an article with the same title, then the API adds a random 6 string suffix.

it would be very nice to show how to test this using the code coverage as a guide

• API test seems the simplest, yet does not verify that the user interface handles the returned slug. Maybe it goes to the original article slug even when it should go to the second article?!
• E2E test seems ideal
  • create both articles via UI
  • confirm first slug
  • confirm the second slug
  • create first article via API call, then create the second article via UI

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: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Missing sourcemap in coverage report

Hello,

My coverage report missing all the sourcemap like this

Does anybody know how to fix it.

Thanks a lot!

The "About" section in the repo says "Condit example blogging app", not "Conduit" 😅

Title says it all 😄

Create post API failing

When I try to create a new post from the UI, it is failing. Below is the snapshot from the console which indicates a 404 error on the POST request. Does anyone have a clue about this?

create data via task and database

Can we use upsert from Objection here?

Hit the API edge case using cy-api test

From the presentation slides

always generate coverage reports for client and server folders

Currently, the names of the files shift depending on if we are running server tests or not. We should always produce the full code coverage reports, even if the reports are empty.

Only instrument front-end code in test environment

Can babel understand environment-specific instrumentation? there was a bug about it in ParcelJS I think.

But we should only be using Istanbul babel plugin when NODE_ENV=test