=begin
#Datadog API V1 Collection

#Collection of all Datadog Public endpoints.

The version of the OpenAPI document: 1.0
Contact: support@datadoghq.com
Generated by: https://openapi-generator.tech
OpenAPI Generator version: 5.0.0-SNAPSHOT

=end

require 'spec_helper'
require 'json'

# Unit tests for DatadogAPIClient::V1::ServiceLevelObjectivesApi
# Automatically generated by openapi-generator (https://openapi-generator.tech)
# Please update as you see appropriate
describe 'ServiceLevelObjectivesApi' do
  before do
    # run before each test
    @api_instance = DatadogAPIClient::V1::ServiceLevelObjectivesApi.new
  end

  after do
    # run after each test
  end

  describe 'test an instance of ServiceLevelObjectivesApi' do
    it 'should create an instance of ServiceLevelObjectivesApi' do
      expect(@api_instance).to be_instance_of(DatadogAPIClient::V1::ServiceLevelObjectivesApi)
    end
  end

  # unit tests for check_can_delete_slo
  # Check if SLOs can be safely deleted
  # Check if a SLO can be safely deleted. For example, assure an SLO can be deleted without disrupting a dashboard.
  # @param ids A comma separated list of the IDs of the service level objectives objects.
  # @param [Hash] opts the optional parameters
  # @return [CheckCanDeleteSLOResponse]
  describe 'check_can_delete_slo test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for create_slo
  # Create a SLO object
  # Create a service level objective object.
  # @param body Service level objective request object.
  # @param [Hash] opts the optional parameters
  # @return [SLOListResponse]
  describe 'create_slo test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for delete_slo
  # Delete a SLO
  # Permanently delete the specified service level objective object.  If an SLO is used in a dashboard, the `DELETE /v1/slo/` endpoint returns a 409 conflict error because the SLO is referenced in a dashboard.
  # @param slo_id The ID of the service level objective.
  # @param [Hash] opts the optional parameters
  # @option opts [String] :force Delete the monitor even if it's referenced by other resources (e.g. SLO, composite monitor).
  # @return [SLODeleteResponse]
  describe 'delete_slo test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for delete_slo_timeframe_in_bulk
  # Bulk Delete SLO Timeframes
  # Delete (or partially delete) multiple service level objective objects.  This endpoint facilitates deletion of one or more thresholds for one or more service level objective objects. If all thresholds are deleted, the service level objective object is deleted as well.
  # @param body Delete multiple service level objective objects request body.
  # @param [Hash] opts the optional parameters
  # @return [SLOBulkDeleteResponse]
  describe 'delete_slo_timeframe_in_bulk test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for get_slo
  # Get a SLO's details
  # Get a service level objective object.
  # @param slo_id The ID of the service level objective object.
  # @param [Hash] opts the optional parameters
  # @return [SLOResponse]
  describe 'get_slo test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for get_slo_history
  # Get an SLO's history
  # Get a specific SLO’s history, regardless of its SLO type.  The detailed history data is structured according to the source data type. For example, metric data is included for event SLOs that use the metric source, and monitor SLO types include the monitor transition history.  **Note:** There are different response formats for event based and time based SLOs. Examples of both are shown.
  # @param slo_id The ID of the service level objective object.
  # @param from_ts The `from` timestamp for the query window in epoch seconds.
  # @param to_ts The `to` timestamp for the query window in epoch seconds.
  # @param [Hash] opts the optional parameters
  # @return [SLOHistoryResponse]
  describe 'get_slo_history test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for list_sl_os
  # Search SLOs
  # Get multiple service level objective objects by their IDs.
  # @param ids A comma separated list of the IDs of the service level objectives objects.
  # @param [Hash] opts the optional parameters
  # @return [SLOListResponse]
  describe 'list_sl_os test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

  # unit tests for update_slo
  # Update a SLO
  # Update the specified service level objective object.
  # @param slo_id The ID of the service level objective object.
  # @param body The edited service level objective request object.
  # @param [Hash] opts the optional parameters
  # @return [SLOListResponse]
  describe 'update_slo test' do
    it 'should work' do
      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
    end
  end

end