hubspot-api-client 1.0.1

data/spec/pipelines/configuration_spec.rb

@@ -0,0 +1,42 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+
+describe Hubspot::Client::Crm::Pipelines::Configuration do
+  let(:config) { Hubspot::Client::Crm::Pipelines::Configuration.default }
+
+  before(:each) do
+    # uncomment below to setup host and base_path
+    # require 'URI'
+    # uri = URI.parse("https://api.hubapi.com/crm/v3/pipelines")
+    # Hubspot.configure do |c|
+    #   c.host = uri.host
+    #   c.base_path = uri.path
+    # end
+  end
+
+  describe '#base_url' do
+    it 'should have the default value' do
+      # uncomment below to test default value of the base path
+      # expect(config.base_url).to eq("https://api.hubapi.com/crm/v3/pipelines")
+    end
+
+    it 'should remove trailing slashes' do
+      [nil, '', '/', '//'].each do |base_path|
+        config.base_path = base_path
+        # uncomment below to test trailing slashes
+        # expect(config.base_url).to eq("https://api.hubapi.com/crm/v3/pipelines")
+      end
+    end
+  end
+end

data/spec/pipelines/models/collection_response_pipeline_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipeline
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'CollectionResponsePipeline' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipeline.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CollectionResponsePipeline' do
+    it 'should create an instance of CollectionResponsePipeline' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipeline)
+    end
+  end
+  describe 'test attribute "results"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "paging"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/collection_response_pipeline_stage_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipelineStage
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'CollectionResponsePipelineStage' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipelineStage.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CollectionResponsePipelineStage' do
+    it 'should create an instance of CollectionResponsePipelineStage' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::CollectionResponsePipelineStage)
+    end
+  end
+  describe 'test attribute "results"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "paging"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/error_detail_spec.rb

@@ -0,0 +1,53 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::ErrorDetail
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ErrorDetail' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::ErrorDetail.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ErrorDetail' do
+    it 'should create an instance of ErrorDetail' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::ErrorDetail)
+    end
+  end
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "_in"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "context"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/error_spec.rb

@@ -0,0 +1,71 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::Error
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'Error' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::Error.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of Error' do
+    it 'should create an instance of Error' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::Error)
+    end
+  end
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "correlation_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "category"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "errors"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "context"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "links"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/next_page_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::NextPage
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'NextPage' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::NextPage.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of NextPage' do
+    it 'should create an instance of NextPage' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::NextPage)
+    end
+  end
+  describe 'test attribute "after"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "link"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/paging_spec.rb

@@ -0,0 +1,41 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::Paging
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'Paging' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::Paging.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of Paging' do
+    it 'should create an instance of Paging' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::Paging)
+    end
+  end
+  describe 'test attribute "_next"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/pipeline_input_spec.rb

@@ -0,0 +1,53 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::PipelineInput
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'PipelineInput' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::PipelineInput.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of PipelineInput' do
+    it 'should create an instance of PipelineInput' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::PipelineInput)
+    end
+  end
+  describe 'test attribute "stages"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "label"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "display_order"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/pipelines/models/pipeline_patch_input_spec.rb

@@ -0,0 +1,53 @@
+=begin
+#CRM Pipelines
+
+#Pipelines represent distinct stages in a workflow, like closing a deal or servicing a support ticket. These endpoints provide access to read and modify pipelines in HubSpot. Pipelines support `deals` and `tickets` object types.  ## Pipeline ID validation  When calling endpoints that take pipelineId as a parameter, that ID must correspond to an existing, un-archived pipeline. Otherwise the request will fail with a `404 Not Found` response.
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 4.2.2
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Hubspot::Client::Crm::Pipelines::Models::PipelinePatchInput
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'PipelinePatchInput' do
+  before do
+    # run before each test
+    @instance = Hubspot::Client::Crm::Pipelines::Models::PipelinePatchInput.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of PipelinePatchInput' do
+    it 'should create an instance of PipelinePatchInput' do
+      expect(@instance).to be_instance_of(Hubspot::Client::Crm::Pipelines::Models::PipelinePatchInput)
+    end
+  end
+  describe 'test attribute "label"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "display_order"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "archived"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end