Bug 4948 - create tests for Toaster API
Summary: create tests for Toaster API
Status: VERIFIED OBSOLETE
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.1
Assignee: Mihail Stanciu
QA Contact: Mihail Stanciu
URL:
Whiteboard:
Depends on: 5015
Blocks:
  Show dependency tree
 
Reported: 2013-07-29 14:11 UTC by Calin Dragomir
Modified: 2015-11-17 13:43 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Calin Dragomir 2013-07-29 14:11:30 UTC 
We need to create some basic tests which will validate that the code is working as expected.
The tests will be ran against the API and will check the response according to our documentation.
Comment 1 Andreea Brandusa Proca 2013-11-05 10:29:32 UTC 
The API tests need to be updated each time the database changes.
I will change the milestone of this bug until the database model will be constant.
Comment 2 Alexandru Damian 2013-11-29 14:16:30 UTC 
APIs must be tested according to the published API documentation, and not internal database structure.
Comment 3 Alexandru Damian 2013-11-29 14:17:23 UTC 
Please document on Wiki, as part of this bug:

- how the tests are to be started
- how tests results are to be intepreted
Comment 4 Ionut Chisanovici 2014-04-09 15:18:11 UTC 
Moved to 1.7
Comment 5 Ionut Chisanovici 2014-10-08 13:48:59 UTC 
This will be moved to 1.8 as the components of the project part of the toaster will be added in 1.8 and the API tests will extend to cover them as well.

Cheers,
Ionut C
Comment 6 Mihail Stanciu 2015-11-17 12:36:37 UTC 
This is obsolete as of 2.0.

Currently there is no public facing API.
Comment 7 Mihail Stanciu 2015-11-17 12:37:00 UTC 
(In reply to comment #6)
> This is obsolete as of 2.0.
> 
> Currently there is no public facing API.

Verified as per above.