testomatio / app Goto Github PK

26.0 4.0 2.0 39 KB

Testomat.io is a simplified test management system for your automated tests. Issues, project board & documentation. app.testomat.io

Home Page: https://app.testomat.io

qa qa-automation software-testing test-management test-automation

app's Introduction

Testomat.io is a test management system for automated and manual tests.

It's a modern QA tool designed to improve the efficiency and effectiveness of software testing processes.

Testomat.io is about shift-left strategy, test automation first approach, continuous integration and continuous delivery, DevOps and TestOps practices.

Schedule a demo to see system in action. No slides. Just practical use cases of QA workflows in real app.

Features

Test Case Management: Allows us to create, manage, and organize our test cases in a structured and systematic manner.
Real-Time Collaboration: Enables our team to collaborate in real-time, ensuring everyone is always on the same page.
Test Run Reports: Provides detailed reports on our test runs, helping us to quickly identify and address any issues.
Integration with CI/CD and tracking tools: Seamlessly integrates with our existing CI/CD tools, allowing for automated test execution. Link test to JIRA, Azure, Github, Gitlab, etc.

Main Benefits

Integration with popular testing frameworks: Testomat.io seamlessly integrates with popular testing frameworks, allowing quick generation of reports for Cypress, CodeceptJS, Codeception, Playwright, TestCafe, Cucumber, Jest, Protractor, Mocha, and Chai, etc
Real-time reporting: Testomat.io provides real-time test result reporting, allowing feedback as soon as a test is completed. This is particularly beneficial for large-scale testing projects where test running goes for hours.
Comprehensive analytics: The test management tool builds a comprehensive real-time quality assurance widgets. Track flakiness, failures, defects, tags, envionrment, test automation coverage, user story coverage, and more.

How to Get Started

Sign up at https://app.testomat.io/
Create a project
Create a test
Run a test
See report

You're done. 🎉

For more information on how to use Testomat.io, please refer to their official documentation.

Tools

Tools that will help you make life easier.

sync classical automated tests by: check-tests
sync bdd / gherkin automated tests by: check-cucumber
report javascript / typescript test results by: reporter
report python / pytest test results by: pytestomatio
report php test results by: php-reporter
report junit xml format test results by: report-xml
jira plugin: plugin on atlassian market

Useful links

docs: https://docs.testomat.io/
changelog: https://changelog.testomat.io/ (we deliver on weekly basis)
test automation demo projects: github.com/testomatio/examples

Support

raise issue / request feature : https://github.com/testomatio/app/issues/new
email us: [email protected]
telegram group: t.me/testomatio_chat
slack: testomatio slack

twitter: twitter.com/testomatio
linkedin: linkedin.com/company/testomatio
facebook: fb.com/testomatio
telegram: t.me/testomatio
slack: testomatio slack
youtube: youtube.com/@testomatio

Contact us

email us: [email protected]
telegram group: t.me/testomatio_chat
slack: testomatio slack

QA and Dev outsourcing

Need to make software testing or test automation for your project?

Please request test automation consulting at zapple.tech or software development services at sdclabs.com

app's People

Contributors

Stargazers

Watchers

Forkers

avramenkodmitry mbiesiad

app's Issues

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

Restrict normal users to edit project settings like framework and language

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

email templates

add test run instructions for cypress.io to start-run

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

webdriverio + mocha support in UI

add raise issue button

create Terms of Service

fix z exception in reporting

reset password gives error all the times

Implement tests for Templates on backend:

cucumber project
codecept project
cypress project

project delete functionality

fix tags placement in scenario editor for CoffeeMachine project

fix "Recordings" page

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

add support button

Add Alert component for success and failure messages

search doesn't work for z project

reset password function gives error

cypress support

add chrome extention to google store

Error reportings on failed requests. User Alert components for that

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.

test cypress demo

makeup backup mechanism for prod and stagging

Create / Update / Delete a Template from UI

wiki instructions how to onboard newbie

logout from project list view

fix invites in admin

test jest support

link draft test to automated test

blocked by #122

history of changes of a test

add crisp support widget for internal pages

edit templates doesn't work

no action is done during clicking on edit button

Fix tests for backend and add more tests for current endpoints

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 

Track current app version, and show it in settings

create production and staging environment

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

TestCafe support

create Privacy Policy

App redirects to home page even if user can't delete the project

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

user acceptance testing by whole dev team

test jest demo

add "Run Command" to test suite

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

hotjar integration

recorder chrome extension doesn't work

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)