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

Actual bugs for intelligence commands #4511

Closed
12 of 13 tasks
Ohrimenko1988 opened this issue Mar 22, 2017 · 7 comments
Closed
12 of 13 tasks

Actual bugs for intelligence commands #4511

Ohrimenko1988 opened this issue Mar 22, 2017 · 7 comments
Assignees
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Mar 22, 2017

In the developing we have new command widget . Actual bugs :

@musienko-maxim musienko-maxim added kind/bug Outline of a bug - must adhere to the bug report template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. and removed kind/bug Outline of a bug - must adhere to the bug report template. labels Mar 22, 2017
@musienko-maxim musienko-maxim changed the title Command widget bugs Actual bugs for intelligence commands Mar 23, 2017
@musienko-maxim
Copy link
Contributor

musienko-maxim commented Mar 23, 2017

@slemeur, @TylerJewell So, QA team are finishing cover the intelligence commands feature with selenium tests. For us very important - our test plan meet acceptance criteria for intelligence commands. Is there sufficient coverage of functionality of this one? Please take a look on this document: https://github.com/codenvy/qa/wiki/Test-plan-of-intelligence-commands-feature

@slemeur
Copy link
Contributor

slemeur commented Mar 23, 2017

Ok thanks.

I have reviewed the issues and closed few that are not bugs.

About the test plan:

  • you need to consider tests around factories used cases (I tested them and they were working).

@musienko-maxim
Copy link
Contributor

In this document describe short user story implemented in the selenium tests: https://docs.google.com/document/d/1zDEEWmxOu53omnkxnG8n3eyii-79utk5qeEZscTeGWg/edit?userstoinvite=ashmaraev@codenvy.com&ts=58db655a
Please answer: will it enough for acceptance?

@musienko-maxim
Copy link
Contributor

Please review the tests for factories may be one of them cover workflow with I.C. If we do not have some usecases, please, provide this one for us. We do this

@slemeur
Copy link
Contributor

slemeur commented Mar 29, 2017

This doc is covering usual factories flows. It is not covering how the new commands are handled in factories.

You should have those user stories related to Intelligent Commands:

  • As a user, I have configured a workspace with commands. Commands are assigned to particular goals. When I'm going to the factories on dashboard, and creating a factory from that workspace I can use that factory and find the commands with the exact same configuration in the newly created workspace.

  • As a user, I'm authoring a factory in json. When I'm defining commands, I can define the goal for each of the commands. When I'm using the factory, the commands are defined to the proper goals.

  • As a user, I have configured a workspace with multiple project and multiple commands. I define a command to be scoped to only a single project. When I'm creating a factory from that workspace, and using it I can see this command only scoped to the same project.

  • As a user, I'm authoring a factory in json. When I'm defining commands, I can define the scope for applicable projects. When I'm using the factory, the commands are properly scoped to the right projects.

  • As a user, I can create my custom goal for commands in my workspace. When I'm creating a factory from that workspace, and using it, I can see commands defined in my custom goal.

  • As a user, I'm authoring a factory in json. If I'm not providing goals to the commands, then when using the factory, the commands will be in the Common goal in the newly created workspace.

@musienko-maxim
Copy link
Contributor

Ok, i will try add this one in the autotests. On this moment we will do this in manual mode.

@TylerJewell
Copy link

In future, we should reserve epics for end user stories and not really use them as just a collection of like-minded bugs.

It was really impressive how much we did here, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
Projects
None yet
Development

No branches or pull requests

4 participants