The app from testomatio

When a normal user tries to delete the project. It should not allow the user to delete it.

Even though it is working, it redirects to home page immediately after showing the error. This may be due to recent error handling changes inn frontend

makeup backup mechanism for prod and stagging

fix description during test import for codeceptjs+cucmber project to understand where feature folder is

reset password gives error all the times

add crisp support widget for internal pages

Error reportings on failed requests. User Alert components for that

Implement tests for Templates on backend:

cucumber project
codecept project
cypress project

no api key mentioned in "Run command" for one test

reset password function gives error

add chrome extention to google store

Track current app version, and show it in settings

Add Alert component for success and failure messages

add "Run Command" to test suite

add "Run Command" to test suite the same as we have for the particular test

Settings: framework & language change

Currently we have framework & lang listed under "Project" section
There should be a way to change them there but by default, this feature should be locked.

When framework or lang is changed user should be warned that their templates will be replaced
Whan user changes from gherkin or to gherkin - they should be notified that project goes to BDD structure and this will affect the UI as well as current templates

Also we should remove changing of framework/lang in "Import" once tests are imported.
User should be taken to Settings/Project instead

edit templates doesn't work

no action is done during clicking on edit button

test cypress demo

add raise issue button

Step description

Steps should also have a description so a user could write where is that step is used, in which context, for which requirements.

An editor will also display that description when autocompletion is triggered.

Create / Update / Delete a Template from UI

cypress demo project execution is not reporting back to testomat

 ~/D/t/t/d/examples    cypress  env TESTOMATIO=dasc04ccfwd0 npx cypress run --spec "cypress/integration/examples/aliasing.spec.js"
It looks like this is your first time using Cypress: 4.6.0

  ✔  Verified Cypress! /Users/poliarush/Library/Caches/Cypress/4.6.0/Cypress.app

Opening Cypress...

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:    4.6.0                                                                              │
  │ Browser:    Electron 80 (headless)                                                             │
  │ Specs:      1 found (examples/aliasing.spec.js)                                                │
  │ Searched:   cypress/integration/examples/aliasing.spec.js                                      │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘


────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  examples/aliasing.spec.js                                                       (1 of 1)


  Aliasing
    ✓ .as() - alias a DOM element for later use (658ms)
    ✓ .as() - alias a route for later use (927ms)


  2 passing (3s)


  (Results)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        2                                                                                │
  │ Passing:      2                                                                                │
  │ Failing:      0                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  0                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     2 seconds                                                                        │
  │ Spec Ran:     examples/aliasing.spec.js                                                        │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘


  (Video)

  -  Started processing:  Compressing to 32 CRF
  -  Finished processing: /Users/poliarush/Documents/temp/testomat/demo1/examples/cyp    (0 seconds)
                          ress/cypress/videos/examples/aliasing.spec.js.mp4


====================================================================================================

  (Run Finished)


       Spec                                              Tests  Passing  Failing  Pending  Skipped
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  examples/aliasing.spec.js                00:02        2        2        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✔  All specs passed!                        00:02        2        2        -        -        -

 ~/D/t/t/d/examples    cypress 

webdriverio + mocha support in UI

fix "Recordings" page

add link to actual test
fix displaying test with empty description
use the same fonts as on frontend

cypress demo project importing is failing with error

TOTAL 114 TESTS FOUND

🚀 Sending data to testomat.io

✖️ Eror while uploading data: Mysql2::Error: Incorrect string value: '\xF0\x9F\x91\x80\x0A ...' for column 'code' at row 1

Fix tests for backend and add more tests for current endpoints

create production and staging environment

fix tags placement in scenario editor for CoffeeMachine project

Autoformat Gherkin scenarios

There is a standard of indenting scenario files written with Gherkin
our editor should reformat this file according to spec

We can take this implementation
https://github.com/drweb86/Gherkin-Beautifier-VS-Code-Plugin/blob/master/extension.js

test jest demo

hotjar integration

Restrict normal users to edit project settings like framework and language

Gherkin scenarios preview mode

Currently, we display Gherkin scenarios in an editor with a read-only view
However, it is

really confusing - people try to edit it, while not on Edit page)
slow - editor is loaded via iframe

We should have gherkin scenarios to be displayed in the same markdown preview, as regular test descriptions, but we can add our own plugin on top of markdown to analyze and highlight Gherkin keywords. (See "Snowdown extensions)

testomatio / app Goto Github PK

app's People

Contributors

Stargazers

Watchers

Forkers

app's Issues

Recommend Projects

Recommend Topics

Recommend Org