compile.feature

Feature: Compile
  Background:
    Given an algod v2 client

  @compile
  Scenario Outline: Compile programs
    When I compile a teal program "<program>"
    Then it is compiled with <status> and "<result>" and "<hash>"
    Examples:
      | program               | status | result   | hash                                                      |
      | programs/one.teal     | 200    | AiABASI= | YOE6C22GHCTKAN3HU4SE5PGIPN5UKXAJTXCQUPJ3KKF5HOAH646MKKCPDA|
      | programs/invalid.teal | 400    |          |                                                           |


  @compile
  Scenario Outline: Teal compiles to its associated binary
    When I compile a teal program "<teal>"
    Then base64 decoding the response is the same as the binary "<program>"
    Examples:
      | teal                          | program                           |
      | programs/one.teal             | programs/one.teal.tok             |
      | programs/zero.teal            | programs/zero.teal.tok            |
      | programs/eight.teal           | programs/eight.teal.tok           |
      | programs/abi_method_call.teal | programs/abi_method_call.teal.tok |

  @compile.sourcemap
  Scenario Outline: Algod compiling Teal returns a valid Source Map
    When I compile a teal program "<teal>" with mapping enabled
    Then the resulting source map is the same as the json "<sourcemap>"
    Examples:
      | teal                | sourcemap                                  |
      | programs/quine.teal | v2algodclient_responsejsons/sourcemap.json |

  @compile.disassemble
  Scenario Outline: SDK requests algod to disassemble valid TEAL bytecode to source code
    Then disassembly of "<bytecodeFilename>" matches "<sourceFilename>"
    Examples:
      | bytecodeFilename                    | sourceFilename                          |
      | programs/eight.teal.tok             | programs/eight_disassembled.teal        |