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-suite] Add new Studio API test cases to cover all the response scenarios for the Studio API Calls #1660

Closed
luishernandezmonge opened this Issue Dec 1, 2017 · 2 comments

Comments

@luishernandezmonge
Member

luishernandezmonge commented Dec 1, 2017

Expected behavior

We need to try to cover all the possible scenarios on each studio api call (e.g: request& response for 400's, 200's, 500's according with each API Call specification)

Actual behavior

-- Partially automated --

Steps to start work on

  • Get the latest version test framework source code on your local
  • Get Eclipse IDE with maven and testing plugging
  • Install Java, Maven and git
  • Get, Build, Deploy and Start craftercms on your local
  • Review the api test cases located on package:
    *Review the main documentation of the Studio API here: http://docs.craftercms.org/en/3.0/developers/projects/studio/api/index.html
    and start automate the pending test cases on the test framework.
    Also, change the Yes/No value for the Automated column on the Crafter CMS Integration Test document

Log/stack trace (use https://gist.github.com)

--

Specs: version, OS, browser, etc.

Mac OS, Linux, Windows

@luishernandezmonge luishernandezmonge self-assigned this Dec 1, 2017

@RLChris-Lim RLChris-Lim self-assigned this Dec 1, 2017

@sumerjabri sumerjabri added this to the Crafter CMS v3.0.3 milestone Dec 6, 2017

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.0.x via automation Dec 6, 2017

@sumerjabri sumerjabri changed the title from [test-suite - new studio API test cases] Add new Studio API test cases to cover all the response scenarios for the Studio API Calls to [test-suite] Add new Studio API test cases to cover all the response scenarios for the Studio API Calls Dec 6, 2017

@luishernandezmonge

This comment has been minimized.

Show comment
Hide comment
@luishernandezmonge

luishernandezmonge Jun 7, 2018

Member

@alhambrav I think that we can close this ticket and separate it into individual tickets for each api call scenarios like: Non-valid parameters, 500 and positive scenarios like 200OK.

All of this new tickets related to uncovered api calls on all api groups (into the integration test document).

Member

luishernandezmonge commented Jun 7, 2018

@alhambrav I think that we can close this ticket and separate it into individual tickets for each api call scenarios like: Non-valid parameters, 500 and positive scenarios like 200OK.

All of this new tickets related to uncovered api calls on all api groups (into the integration test document).

@alhambrav

This comment has been minimized.

Show comment
Hide comment
@alhambrav

alhambrav Jun 7, 2018

Member

@luishernandezmonge Sounds good. I'll add them to the document and create tickets accordingly.

Member

alhambrav commented Jun 7, 2018

@luishernandezmonge Sounds good. I'll add them to the document and create tickets accordingly.

@alhambrav alhambrav closed this Jun 7, 2018

Crafter CMS v3.0.x automation moved this from Backlog to Completed Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment