Also, names should_return_the_correct_properties_for_given_sum, Should_pass_shuffled_tests, and Should_pass_random_tests are not uniformly formatted. All of them either should start with uppercase or lowercase.

I also would like to add that creating a new random engine for every test is rudimentary. Describe is a struct, so this has to be done instead:

Describe(Pyramid_Property_Sum)
{
private:
    std::mt19937 rng{ std::random_device{}() };

public:
    
    It(should_return_the_correct_properties_for_given_sum)
    {
        // ...
    }

    // ...
};

Looks pretty good! Couple of notes (first three are important; third is stylistic):

• std::vector<int> is a poor fit for this Kata since the return value should carry exactly 4 items. Choose any of the following instead:
  • std::tuple<int, int, int, int>. If you think it's too wordy, do using PyramidInfo = std::tuple<int, int, int, int>; and use the alias PyramidInfo thereafter. Include <tuple> for this one
  • std::array<int, 4>. Include <array> for this one
  • struct PyramidInfo { int vertices; int edges; int faces; int sides; };
• Remove the #include out of preloaded and instead put it explicitly in the solution setup. Do not hide headers (and yes, this means you also need to #include <utility> wherever you use std::pair).
• Add failure messages to help the solver on failure. Ex: Assert::That(pyramid(sumValue), Equals(expected), ExtraMessage("Incorrect output for sum = " + std::to_string(sumValue)));. Include <string> for this one. For fixed tests just hardcode the ExtraMessages.
• The submission tests look pretty good. My only tips are that you can do std::mt19937 rng{ std::random_device{}() }; in one line rather than 3. Also, the C++ distributions are inclusive, so you don't need to add 1 to the end value -- distr(150, 10000) is what you probably intended.

Nice and mathy kata to learn some theory with.

actually very informative, thank you

Also, make it accessble using request.form.get as well

Specified to use POST request parameter "code" but was not found in attempt test. OK, it makes sense for the usual test, I use an if-else statement to catch if it's None, but it's always None. Great idea once again, but requires some fixing

Great kata idea! However, sometimes the code runs too slow and won't fit inside of the time limit. Try using a

@test.timeout(seconds)
def something():
    #Tests go here
    pass

For more documentation, refer to https://docs.codewars.com/languages/python/codewars-test/

and your code with a literal import statement within function is efficient?

pewhapz we needs more sample tests?

because there are only 2 of them and they do not catch your specific error

what
how is sample test working fine then

your condition is wrong

You're splitting the string twice in the above code, whereas by adding the extra line you only split the string by spaces once.