ftc_api_v3_client 0.1.0

data/spec/api/events_api_spec.rb

@@ -0,0 +1,207 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for FtcApiV3Client::EventsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'EventsApi' do
+  before do
+    # run before each test
+    @api_instance = FtcApiV3Client::EventsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of EventsApi' do
+    it 'should create an instance of EventsApi' do
+      expect(@api_instance).to be_instance_of(FtcApiV3Client::EventsApi)
+    end
+  end
+
+  # unit tests for get_event
+  # Get event from season
+  # Get detailed information about a single event
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Event]
+  describe 'get_event test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_advancement_from
+  # Get event advancement (from)
+  # Gets advancement list for teams advancing from this event to the next level of competition
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3AdvancementFrom]
+  describe 'get_event_advancement_from test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_alliance_selections
+  # Get event alliance selections
+  #         Gets alliance selection operations for the given event, including accepts and declines. These         are presented in the order in which they occurred. Refer to the season's competition manual to         confirm the order of alliance selections that year. If you are looking for the final alliances         and are not interested in analyzing the selection process itself, we recommend using the         GetEventAlliances endpoint instead. 
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3AllianceSelections]
+  describe 'get_event_alliance_selections test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_alliances
+  # Get event alliances
+  # Gets playoff alliances for the given event
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3PlayoffAlliances]
+  describe 'get_event_alliances test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_awards
+  # Get event awards
+  # Gets award information and recipients for the given event.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Awards]
+  describe 'get_event_awards test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_match
+  # Get match details
+  # Gets details for a single match, including season-specific score details.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param tournament_level The tournament level of the match
+  # @param series The series of the match (0 for non-playoff matches). For remote events, the team number for the match.
+  # @param number The match number
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3MatchDetails]
+  describe 'get_event_match test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_pit_map
+  # Get pit map
+  # Gets data representation of pit map
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3PitMap]
+  describe 'get_event_pit_map test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_playoff_rankings
+  # Get event playoff rankings
+  # Gets playoff rankings for a given event. Each sort order field is season-specific: see the season's competition manual for definitions. Only applicable to events using round-robin playoffs (e.g. FIRST Championship da Vinci)
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3PlayoffRankings]
+  describe 'get_event_playoff_rankings test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_playoff_structure
+  # Get playoff structure
+  # Gets programmatic description of the playoff structure (e.g. bracket) structure for event. Contains sufficient information to construct a bracket display.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3PlayoffStructure]
+  describe 'get_event_playoff_structure test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_event_rankings
+  # Get event rankings
+  # Gets rankings for a given event. Each sort order field is season-specific: see the season's competition manual for definitions. Do not use for league meets or multi-division parent events
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Rankings]
+  describe 'get_event_rankings test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_event_matches
+  # List event matches
+  # Gets matches for a given event. Includes winner and score information if available. Score details must be fetched per match.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @option opts [ApiV3TournamentLevel] :phase Filter matches to a specific phase
+  # @return [ApiV3Matches]
+  describe 'list_event_matches test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_event_teams
+  # List teams for an event
+  # Lists all teams competing at the event. This includes division assignments if published for this event (and this event is a multi-division parent event). In some cases, teams may be award recipients but not returned in this list. Their information can be fetched individually by number.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param event_code The code (abbreviation) for the event
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3EventParticipants]
+  describe 'list_event_teams test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_events
+  # List events for a season
+  # Lists all events for a season
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Events]
+  describe 'list_events test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/leagues_api_spec.rb

@@ -0,0 +1,104 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for FtcApiV3Client::LeaguesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'LeaguesApi' do
+  before do
+    # run before each test
+    @api_instance = FtcApiV3Client::LeaguesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of LeaguesApi' do
+    it 'should create an instance of LeaguesApi' do
+      expect(@api_instance).to be_instance_of(FtcApiV3Client::LeaguesApi)
+    end
+  end
+
+  # unit tests for get_league
+  # Gets a single league from a region
+  # Gets a leagues for a region in a season, including any children
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param league_code The code (abbreviation) for the league
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3LeagueDetails]
+  describe 'get_league test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_league_rankings
+  # Get rankings for a league
+  # Gets league rankings for a given league. This only includes matches played in League Meets. For rankings including the League Tournament, use the tournament event's rankings endpoint instead. Each sort order field is season-specific: see the season's competition manual for definitions. The last non-zero sort order is the scoring system randomly generated tiebreaker value.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param league_code The code (abbreviation) for the league
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Rankings]
+  describe 'get_league_rankings test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_league_events
+  # List events for a league
+  # Lists all events in a league, including events in child leagues.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param league_code The code (abbreviation) for the league
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Events]
+  describe 'list_league_events test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_league_teams
+  # List teams for a league
+  # Lists all teams assigned to the given league.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param league_code The code (abbreviation) for the league
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Teams]
+  describe 'list_league_teams test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_leagues
+  # Lists leagues for a region
+  # Lists all leagues for a region in a season. Parent/child relationships can be determined from the `parentCode` field of each league. League parents are guaranteed to be in the same region as their children.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Leagues]
+  describe 'list_leagues test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/regions_api_spec.rb

@@ -0,0 +1,86 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for FtcApiV3Client::RegionsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'RegionsApi' do
+  before do
+    # run before each test
+    @api_instance = FtcApiV3Client::RegionsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of RegionsApi' do
+    it 'should create an instance of RegionsApi' do
+      expect(@api_instance).to be_instance_of(FtcApiV3Client::RegionsApi)
+    end
+  end
+
+  # unit tests for get_region
+  # Get region from a season
+  # Gets details for a single region for a season.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Region]
+  describe 'get_region test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_region_events
+  # List events for a regions
+  # Lists all events in a region
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Events]
+  describe 'list_region_events test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_region_teams
+  # List teams for a region
+  # Lists all registered teams assigned to the given region.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param region_code The code (abbreviation) for the region
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Teams]
+  describe 'list_region_teams test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_regions
+  # List regions for a season
+  # Lists all active regions for a season.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Regions]
+  describe 'list_regions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/seasons_api_spec.rb

@@ -0,0 +1,58 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for FtcApiV3Client::SeasonsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'SeasonsApi' do
+  before do
+    # run before each test
+    @api_instance = FtcApiV3Client::SeasonsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of SeasonsApi' do
+    it 'should create an instance of SeasonsApi' do
+      expect(@api_instance).to be_instance_of(FtcApiV3Client::SeasonsApi)
+    end
+  end
+
+  # unit tests for get_season
+  # Get single FTC season
+  # Lists basic information about the given FTC season
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Season]
+  describe 'get_season test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_seasons
+  # List all FTC seasons
+  # Lists basic information about all FTC seasons with data available through this API
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Seasons]
+  describe 'list_seasons test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/teams_api_spec.rb

@@ -0,0 +1,97 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for FtcApiV3Client::TeamsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'TeamsApi' do
+  before do
+    # run before each test
+    @api_instance = FtcApiV3Client::TeamsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of TeamsApi' do
+    it 'should create an instance of TeamsApi' do
+      expect(@api_instance).to be_instance_of(FtcApiV3Client::TeamsApi)
+    end
+  end
+
+  # unit tests for get_team
+  # Get teams information
+  # Get information for a specific team. If a team's number changed during the season, this endpoint can be called with the old number and it will return the new one.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param number The team's number
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Team]
+  describe 'get_team test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_team_details
+  # Get detailed team information
+  # Get detailed information for a specific team. Includes all awards, events, matches, and leagues. If a team's number changed during the season, this endpoint can be called with the old number and it will return the new one.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param number The team's number
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3TeamDetails]
+  describe 'get_team_details test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_team_history
+  # Get team history
+  # Get cross-season history for a specific team number. General information will be from the last season the team competed in.
+  # @param number The team's number
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3TeamHistory]
+  describe 'get_team_history test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_team_avatars
+  # List team avatars for a season
+  # Lists all current team avatars for a season. If all you need is to display avatars with the standard FIRST fallback and scaling, directly link `/avatars/composed/{cmpYear}.css` instead of using this endpoint. Use a div with the classes `team-avatar` and `team-{number}` to display the avatar. Use the css variable `--avatar-size` to control the size of the avatar in px (defaults to 40).
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3TeamAvatars]
+  describe 'list_team_avatars test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_teams
+  # List teams for a season
+  # Lists all registered teams for the given FTC season. In some cases, teams with incomplete registrations may be included in event results but not returned in this list. Use the event's team list for that information if necessary.
+  # @param cmp_year The year of the FIRST Championship for the requested season
+  # @param [Hash] opts the optional parameters
+  # @return [ApiV3Teams]
+  describe 'list_teams test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/api_v3_advancement_from_slot_spec.rb

@@ -0,0 +1,54 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for FtcApiV3Client::ApiV3AdvancementFromSlot
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe FtcApiV3Client::ApiV3AdvancementFromSlot do
+  #let(:instance) { FtcApiV3Client::ApiV3AdvancementFromSlot.new }
+
+  describe 'test an instance of ApiV3AdvancementFromSlot' do
+    it 'should create an instance of ApiV3AdvancementFromSlot' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(FtcApiV3Client::ApiV3AdvancementFromSlot)
+    end
+  end
+
+  describe 'test attribute "team"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "criteria"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "status"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "points"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/api_v3_advancement_from_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#FTC Scoring Data API
+
+#THIS API IS CURRENTLY IN EARLY DEVELOPMENT AND MAY CHANGE WITHOUT WARNING. THIS PAGE WILL BE UPDATED ONCE THE API IS OFFICIALLY RELEASED.  This API provides event and scoring data for FIRST Tech Challenge. Applications that present result data directly are encouraged to directly call this API rather than maintaining their own copies of the data. All endpoints are cached by our CDN and may return data up to one hour old for data that changes infrequently. During an event, data that changes frequently (e.g. match results and rankings) should not be more than 30 seconds old.  NOTE: For developers who have integrated with the v2 API in the past, this is a policy shift, as previously developers were encouraged to maintain their own copy of relevant data. In the interest of providing the community with the most up-to-date data and reducing the burden for applications that are not performing their own analytics on event data, we are now encouraging directly integrating our API into websites and apps.  Also note that all endpoints that accept a year argument now expect the year in which the FIRST Championship for that season is held. This is a change from the previous API and FTC-events website, which used the kickoff year.  To report any issues, please report an issue here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-bug-report.md To request additional data, please submit a feature request here: https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/new?template=api-feature-request.md 
+
+The version of the OpenAPI document: v3
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.20.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for FtcApiV3Client::ApiV3AdvancementFrom
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe FtcApiV3Client::ApiV3AdvancementFrom do
+  #let(:instance) { FtcApiV3Client::ApiV3AdvancementFrom.new }
+
+  describe 'test an instance of ApiV3AdvancementFrom' do
+    it 'should create an instance of ApiV3AdvancementFrom' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(FtcApiV3Client::ApiV3AdvancementFrom)
+    end
+  end
+
+  describe 'test attribute "advancing_team_count"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "slots"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "target_event_code"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end