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.

Sign up for GitHub

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

Jump to bottom

As an SDET, I want tests that ensure LIGO CLI commands can be run from VS Code command palette so that the team can be confident that LIGO has feature parity between TVSCE and TCLI #645

Closed
sinapsist opened this issue Apr 28, 2022 · 3 comments
Closed

As an SDET, I want tests that ensure LIGO CLI commands can be run from VS Code command palette so that the team can be confident that LIGO has feature parity between TVSCE and TCLI #645

sinapsist opened this issue Apr 28, 2022 · 3 comments
Assignees
@michaelkernaghan
Labels
testing Testing related issues VsCE Vs Code Extension Related Work
Milestone
VS Code Extension...

Comments

@sinapsist
Copy link
Contributor

sinapsist commented Apr 28, 2022 •
edited
Loading

As an SDET I want to add tests to verify that the next CLI commands can run from VS Code command palette:

  • @command:taqueria.install @taqueria/plugin-ligo
  • @command:taqueria.compile_ligo
@sinapsist sinapsist added the testing Testing related issues label Apr 29, 2022
@hu3man hu3man added this to the VS Code Extension Improvements milestone May 11, 2022
@sinapsist sinapsist self-assigned this May 13, 2022
@hu3man hu3man moved this from Inbox to Sprint Backlog in 📬 Inbox and Triage May 16, 2022
@hu3man hu3man changed the title Add automated tests for ligo plugin commands for VS Code Extension As an SDET, I want tests that ensure LIGO CLI commands can be run from VS Code command palette so that the team can be confident that LIGO has feature parity between TVSCE and TCLI May 26, 2022
@hu3man hu3man moved this from Sprint Backlog to In Progress in 📬 Inbox and Triage Jun 6, 2022
@hu3man
Copy link
Contributor

hu3man commented Jun 22, 2022

Closing: adding to #605

@hu3man hu3man closed this as completed Jun 22, 2022
Repository owner moved this from In Progress to Done / Closed in 📬 Inbox and Triage Jun 22, 2022
@hu3man
Copy link
Contributor

hu3man commented Oct 18, 2022

@michaelkernaghan for context

@hu3man hu3man reopened this Oct 18, 2022
Repository owner moved this from 🙅‍♂️ Won't Do / Closed to 📫 Inbox in 📬 Inbox and Triage Oct 18, 2022
@hu3man hu3man assigned michaelkernaghan and unassigned sinapsist Oct 18, 2022
@ac10n ac10n added the VsCE Vs Code Extension Related Work label Oct 27, 2022
@michaelkernaghan
Copy link
Contributor

dupe of #1650

@github-project-automation github-project-automation bot moved this from 📫 Inbox to 🙅‍♂️ Won't Do / Closed in 📬 Inbox and Triage Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelkernaghan michaelkernaghan

Labels
testing Testing related issues VsCE Vs Code Extension Related Work
Projects
None yet
Milestone
VS Code Extension Improvements
Development

No branches or pull requests
4 participants
@ac10n @sinapsist @hu3man @michaelkernaghan