Implementing smoke tests with TAP-compliant output format

[pulimsr]

Description of changes: added a .sh and .py file for implementing smoke tests

Check all that applies:

• Did a review by yourself.
• Added proper tests to cover this PR. (If tests are not applicable, explain.)
• Checked if this PR is a breaking (APIs have been changed) change.
• Checked if this PR will not introduce cross-platform inconsistent behavior.
• Checked if this PR would require a ReadMe/Wiki update.

Check which platforms you have built SDK on to verify the correctness of this PR.

• Linux
• Windows
• Android
• MacOS
• IOS
• Other Platforms

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sbiscigl]

we should still leave this off by default, we should enable it in our CI by passing -DENABLE_SMOKE_TESTS=ON to the cmake command found here

[sbiscigl]

lets just remove it instead of commenting it

[sbiscigl]

remove this file from the PR, it gets re-shuffled each time it code gens, we should fix that, but lets leave it out of this PR

[sbiscigl]

its already 1.61.0 in main, you should rebase your branch against main

[sbiscigl]

Green, Bold, and Reset are used to color/format output in a terminal if used in a print statement i.e.

GREEN = '\033[32m'
RESET = '\033[0m'

print(GREEN + "This text will be green." + RESET)
print("This text will be in the default color.")

however these variables are unused -- why do we define then never use them?

[sbiscigl]

shouldnt we hard fail if the env var AWS_SMOKE_TEST_SERVICE_IDS isnt present? i

[sbiscigl]

lets leave std::cout checking out of this, and remove writing from std::cout from the tests.This actually will break our format because both gtest and our custom test logic will all write to the same place corrupting the output, instead we should use the gtest output format feature to make this easier for the example

#include <gmock/gmock.h>
#include <gtest/gtest.h>

using namespace testing;

class SolutionTest : public Test {};

TEST_F(SolutionTest, ShouldWork) {
  ASSERT_TRUE(true);
}

TEST_F(SolutionTest, ShouldAlsoWork) {
  ASSERT_FALSE(true);
}

if we invoke this with

./test_executable --gtest_output=json:output.json > /dev/null

in output.json we will see

{
  "tests": 2,
  "failures": 1,
  "disabled": 0,
  "errors": 0,
  "timestamp": "2025-08-21T10:53:01Z",
  "time": "0s",
  "name": "AllTests",
  "testsuites": [
    {
      "name": "SolutionTest",
      "tests": 2,
      "failures": 1,
      "disabled": 0,
      "errors": 0,
      "timestamp": "2025-08-21T10:53:01Z",
      "time": "0s",
      "testsuite": [
        {
          "name": "ShouldWork",
          "file": "\/Users\/sbiscigl\/untitled\/test\/ltest.cpp",
          "line": 12,
          "status": "RUN",
          "result": "COMPLETED",
          "timestamp": "2025-08-21T10:53:01Z",
          "time": "0s",
          "classname": "SolutionTest"
        },
        {
          "name": "ShouldAlsoWork",
          "file": "\/Users\/sbiscigl\/untitled\/test\/test.cpp",
          "line": 16,
          "status": "RUN",
          "result": "COMPLETED",
          "timestamp": "2025-08-21T10:53:01Z",
          "time": "0s",
          "classname": "SolutionTest",
          "failures": [
            {
              "failure": "\/Users\/sbiscigl\/untitled\/test\test.cpp:17\nValue of: true\n  Actual: true\nExpected: false\n",
              "type": ""
            }
          ]
        }
      ]
    }
  ]
}

so the idea here would be to run the test with --gtest_output=json:output.json > /dev/null then parse the resulting json, transforming it into the TAP output format