Remove remains of cypress

I love cypress already. However my suggestion is to create a separate
repository that includes `backend` and `web` run full stack tests from
there. It is possible to trigger builds in other repositories on Travis
CI. So here is my suggestion: We agree to have matching branch names in
all related repositories, so `branch-1` in repo `web`, `backend` and
`human-connection`.

As a start, the developer has to manually update the submodules in the
meta repository and trigger a build to run fullstack tests. In the
future we might automate this process by triggering builds in other
repos. That's possible on Travis CI, see:
https://docs.travis-ci.com/user/triggering-builds/

See each repository is responsible to keep their set of unit/integration
tests but the meta repository is responsible of carrying out full stack
testing.

@appinteractive your opinion?
This commit is contained in:
Robert Schäfer 2018-12-06 15:07:14 +01:00
parent 77cbf410d6
commit 38f27743f2
7 changed files with 0 additions and 143 deletions

View File

@ -1,5 +1,4 @@
node_modules
build
.nuxt
cypress/
styleguide/

2
.gitignore vendored
View File

@ -75,5 +75,3 @@ dist
# TEMORIRY
static/uploads
cypress/videos

View File

@ -1,5 +0,0 @@
{
"name": "Using fixtures to represent data",
"email": "hello@cypress.io",
"body": "Fixtures are a great way to mock data for responses to routes"
}

View File

@ -1,73 +0,0 @@
/// <reference types="Cypress" />
const loginTestUser = function () {
// Visiting our app before each test removes any state build up from
cy.visit('http://localhost:3000/')
.get('.layout-blank')
.should('be.visible')
cy.location('pathname')
.should('contain', '/login')
cy.get('input[name=email]')
.as('inputEmail')
.should('be.empty')
.and('have.attr', 'placeholder', 'Deine E-Mail')
.trigger('focus')
.type('user@example.org')
cy.get('input[name=password]')
.as('inputPassword')
.should('be.empty')
// .and('have.attr', 'placeholder', 'Dein Passwort')
.trigger('focus')
.type('1234')
cy.get('button[name=submit]')
.as('submitButton')
.should('be.visible')
.and('not.be.disabled')
.click()
cy.get('@submitButton')
.should('be.disabled')
// .next('.snackbar')
cy.get('.layout-default')
cy.location('pathname')
.should('eq', '/')
}
const logout = function () {
cy.visit('http://localhost:3000/logout')
cy.location('pathname')
.should('contain', '/login')
cy.get('.layout-blank')
.should('be.visible')
}
context('Authentication', () => {
it('Login Testuser', loginTestUser)
it('Login & Logout', function () {
// login
loginTestUser()
// logout
logout()
})
it('Still logged in after page-reload', function () {
// login
loginTestUser()
cy.reload()
.get('.layout-default')
// logout
// logout()
})
})

View File

@ -1,17 +0,0 @@
// ***********************************************************
// This example plugins/index.js can be used to load plugins
//
// You can change the location of this file or turn off loading
// the plugins file with the 'pluginsFile' configuration option.
//
// You can read more here:
// https://on.cypress.io/plugins-guide
// ***********************************************************
// This function is called when a project is opened or re-opened (e.g. due to
// the project's config changing)
module.exports = (on, config) => {
// `on` is used to hook into various events Cypress emits
// `config` is the resolved Cypress config
}

View File

@ -1,25 +0,0 @@
// ***********************************************
// This example commands.js shows you how to
// create various custom commands and overwrite
// existing commands.
//
// For more comprehensive examples of custom
// commands please read more here:
// https://on.cypress.io/custom-commands
// ***********************************************
//
//
// -- This is a parent command --
// Cypress.Commands.add("login", (email, password) => { ... })
//
//
// -- This is a child command --
// Cypress.Commands.add("drag", { prevSubject: 'element'}, (subject, options) => { ... })
//
//
// -- This is a dual command --
// Cypress.Commands.add("dismiss", { prevSubject: 'optional'}, (subject, options) => { ... })
//
//
// -- This is will overwrite an existing command --
// Cypress.Commands.overwrite("visit", (originalFn, url, options) => { ... })

View File

@ -1,20 +0,0 @@
// ***********************************************************
// This example support/index.js is processed and
// loaded automatically before your test files.
//
// This is a great place to put global configuration and
// behavior that modifies Cypress.
//
// You can change the location of this file or turn off
// automatically serving support files with the
// 'supportFile' configuration option.
//
// You can read more here:
// https://on.cypress.io/configuration
// ***********************************************************
// Import commands.js using ES2015 syntax:
import './commands'
// Alternatively you can use CommonJS syntax:
// require('./commands')