Skip to content

Latest commit

 

History

History
104 lines (97 loc) · 3.65 KB

Notes.md

File metadata and controls

104 lines (97 loc) · 3.65 KB
Raw

Notes

Unit Tests notes

You must not rely on only Unit Tests to ensure that fetched data is correct. Their purpose here to test and debug certain functions of certain libraries in development stage.

Always make sure that data that you fetched is correct with Riot Developer Portal values with values in Debugger inspectors for validity.

Not all tests expected to complete successfully due to changes in fetched data. You are required to provide your own data for tests to expect them complete successfully!

Clash Tournaments tests cannot be always completed successfully due to perodic nature of Clash Tournaments, so expect some tests fail when there are no active or upcoming Clash Tournaments

For champion rotations tests it is necessary to change values with correct values that were fetched from Riot Developer Portal because of periodic nature of Champion Rotations

Features TODO:

All features to be implemented

  • Move tests settings from constants in .runsettings file
  • Riot APIs
    • Common library
    • Account API
    • League of Legends APIs
      • Champion Rotations API
      • Clash API
      • Mastery API
      • Summoner API
      • Leagues API
      • Challanges API
      • Match API
      • Spectator API
      • Tournament APIs
        • Tournament API
        • Tournament Stub API
    • Status APIs
    • Valorant APIs
      • Ranked API
      • Content API
    • Legends of Runeterra APIs
      • LoR Match API
      • LoR Ranked API
    • TFT APIs
      • Leagues API
      • Match API
      • Summoner API
    • League of Legends Client APIs
      • All game data endpoint
        • GET
        • /liveclientdata/allgamedata
        • query: int: eventID
      • Active player data endpoint
        • GET
        • /liveclientdata/activeplayer
      • Active player abilities endpoint
        • GET
        • /liveclientdata/activeplayerabilities
      • Active player name endpoint
        • GET
        • /liveclientdata/activeplayername
      • Active player runes endpoint
        • GET
        • /liveclientdata/activeplayerrunes
      • Event data endpoint
        • GET
        • /liveclientdata/eventdata
        • query: int: eventID
      • Game stats endpoint
        • GET
        • /liveclientdata/gamestats
      • Players items endpoint
        • GET
        • /liveclientdata/playeritems
        • query: string: summonerName
      • Player list endpoint
        • GET
        • /liveclientdata/playerlist
        • query: enum: teamID {ALL, UNKNOWN, CHAOS, ORDER, NEUTRAL}
      • Player main runes endpoint
        • GET
        • /liveclientdata/playermainrunes
        • query: string: summonerName
      • Player scores endpoint
        • GET
        • /liveclientdata/playerscores
        • query: string: summonerName
      • Player summoner spells endpoint
        • GET
        • /liveclientdata/playersummonerspells
        • query: string: summonerName
    • Replay API
  • Riot Data Dragon API
    • Static data requests from game constants (or from custom Git Repository static JSON files)
    • Multiple Data Dragon providers (Riot Official, Community Data Dragon)
    • More Features TBD

Current WIP

  • find more information about API response objects
    • perform more research about match timeline frame event types
    • find info about "bannerAccent" property for player client preferences
    • find info about "game_outcome" tie value in LoR match
    • find info about League Client game end event result values
  • TBD