Skip to content

[EE] Automate the basic API tests in a QA scenario

Rémy Coutable requested to merge ee-qa-251-api-tests into master

EE MR for https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19280.

What does this MR do?

This automate basic API tests that:

  1. Create a project
  2. Create a file in the repository of the project
  3. Get the file content
  4. Delete the file
  5. Get the tree
  6. Delete the project

Are there points in the code the reviewer needs to double check?

I don't think so.

Why was this MR needed?

This replaces the manual steps under "Basic API tests" here: https://docs.google.com/spreadsheets/u/1/d/1oy5ZtFyT7O4xR02Go0lPyhB5ar0L-Pg7tLVSks8oJ2Q/edit#gid=0

Does this MR meet the acceptance criteria?

  • Tests added for this feature/bug
  • Conform by the code review guidelines
    • Has been reviewed by a Backend maintainer
  • EE specific content should be in the top level /ee folder
  • Conform by the merge request performance guides
  • Conform by the style guides
  • If you have multiple commits, please combine them into a few logically organized commits by squashing them
  • Internationalization required/considered
  • If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Edited by Grzegorz Bizon

Merge request reports