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

test cases: ensuring the "code complete" work meets requirements #61

Open
vjeffrey opened this issue Mar 29, 2019 · 0 comments
Open

test cases: ensuring the "code complete" work meets requirements #61

vjeffrey opened this issue Mar 29, 2019 · 0 comments
Labels
iamv2 This issue or pull request applies to iamv2 work for Automate

Comments

@vjeffrey
Copy link

the basic upgrade path
run chef-automate iam version: expect response of IAM v1.0
create local user
add compliance nodes (chef_load_compliance_scans -N 10). this will create nodes for client runs and compliance.
add some actions (chef_load_actions)
run the upgrade command: chef-automate iam upgrade-to-v2 --beta2.1
logged in as admin:

  • navigate to client runs: expect to see the nodes
  • navigate to compliance: expect to see the nodes
  • navigate to event feed: expect to see the actions

logged in as local user:

  • navigate to client runs: expect to see the nodes
  • navigate to compliance: expect to see the nodes
  • navigate to event feed: expect to see the actions

creating node ingestion rules tags node reports with projects (client runs AND compliance)
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the nodes.
request all nodes without projects (via api or ui)
expect to only the nodes that did not match the ingestion rules ("unassigned")
a) request all nodes in one project: ensure data matches
b) request all nodes in both projects: ensure data matches
c) request all nodes in both projects and all nodes that did not match: expect to see all nodes (a + b)
add more nodes.
repeat a, b, and c from above


creating actions ingestion rules tags actions (events) with projects
note: this does not apply to events from scan jobs and profiles. this only refers to "actions"
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the actions.
request all actions without projects (via api or ui)
expect to only the actions that did not match the ingestion rules ("unassigned")
a) request all actions in one project: ensure data matches
b) request all actions in both projects: ensure data matches
c) request all actions in both projects and all that did not match: expect to see all actions (a + b)
add more actions.
repeat a, b, and c from above


data access integrity
< after upgrading to iamv2 >
while logged in as admin, request nodes from the earlier referenced projects
navigate to the node details view for one of the nodes in client runs. save the url.
navigate to the node details view for one of the nodes in compliance. save the url.
log in as a different user, that does not have access to the projects
copy and paste the urls; expect 403

@vjeffrey vjeffrey transferred this issue from another repository Apr 14, 2019
@vjeffrey vjeffrey added this to the iamv2: ingested nodes & actions milestone Apr 14, 2019
@vjeffrey vjeffrey added iamv2 This issue or pull request applies to iamv2 work for Automate chef-conf This issue is being targeted for delivery by chef conf labels Apr 14, 2019
@vjeffrey vjeffrey removed the chef-conf This issue is being targeted for delivery by chef conf label Apr 29, 2019
@vjeffrey vjeffrey removed this from the iamv2: ingested nodes & actions milestone Jun 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iamv2 This issue or pull request applies to iamv2 work for Automate
Projects
None yet
Development

No branches or pull requests

1 participant