Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in grakn console, transaction my_database schema rea opens up a write transaction #127

Closed
JonThom opened this issue Feb 15, 2021 · 1 comment

Comments

@JonThom
Copy link

JonThom commented Feb 15, 2021

Description

in grakn console, I accidentally hit enter after typing the incomplete command transaction test schema rea
this then opened up a write transaction:

test::schema::write>

Environment

  1. OS (where Grakn server runs): Mac OS 10
  2. Grakn version (and platform): Grakn Core 2.0.0-alpha-6
  3. Grakn client: N/A

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. grakn server
  2. grakn console
  3. database create my_database
  4. transaction my_database schema rea

Expected Output

Unrecognised command, please check help menu

Actual Output

test::schema::write>

@JonThom JonThom changed the title in grakn console, transaction test schema rea opens up a write transaction in grakn console, transaction my_database schema rea opens up a write transaction Feb 15, 2021
@vmax vmax transferred this issue from vaticle/typedb Feb 17, 2021
@haikalpribadi
Copy link
Member

Thanks for raising this issue, @JonThom !! :) We've fixed this issue in commit b96124d and it will come out in the next console release.

@haikalpribadi haikalpribadi self-assigned this Feb 17, 2021
lolski pushed a commit to lolski/typedb-console that referenced this issue Jun 9, 2021
## What is the goal of this PR?

We introduced behavioural tests in alignment with the behavioural tests present in our other clients and core server. This also comes with a more comprehensive set of automated tests, split up in a more sensible way, including but not limited to local integration testing, behavioural tests, and automatic linting checks at the build level.

## What are the changes implemented in this PR?

Behavioural test step definitions added for the Concept and Connection packages.
General testing infrastructure has been added to allow for running a grakn server artifact for testing purposes.
Test folder has been sorted more cleanly to reflect what is needed for what tests.
Linting pass has been added to the build workflow.
Testing has been broken up across multiple workflows- test-behaviour and test-integration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants