6 kyu

Identifying Codewars' Bad Kata Authors

Description
Loading description...
SQL
Databases
  • Please sign in or sign up to leave a comment.
  • ejini战神 Avatar

    Codewars' admin gonna love this one as it aids their promotional campaign ^^

    Also, looking forward to more katas from you (Maybe good translators who update a lot of content / bad beta solvers who constantly spam 7-8kyu ranks on votes / hardworking mods who always track down cheaters / copycats XD) ^^

  • Ciprian Amza Avatar

    Nice kata! :)

  • Blind4Basics Avatar

    Hi,

    • Would it be possible to have more than one single sample test? (true question: I know shit to authoring sql kata) Generally, with one single sample test, only a tiny part of the specs is tested which turns out to be very annoying (on user's side)
    • Would it be possible to have meaningful data visible in the example tests? Like, staring at the name of the test function has absolutely no interest for the user. Would it be possible to see the table definition there? or at least the values used to define the table(s)? Training in sql looks to me like a f... hassle because of this (I need to rewrite entire queries just to dig information out of the tests, this is really cumbersome/painflul)

    Cheers

    • bornForThis Avatar

      Bonjour!

      1. Yes, it is definitely possible to create more than one single test: For that, it is needed to populate a table with sample data for the first test, compare it with the expected result, truncate the table, and afterwards repeat population and checking the correctness of the solution. I always made only one sample test which usually covers most part of the specs; often supplementing it with additional static tests on submitting the final solution.
      2. Yes, it is possible to have a meaningful data visible in the example tests. I started recently doing that, like, for example, on this kata Also recently found a way to make a parametrized SQL katas, and I display example tests very similar to typical Codewars tests: for example, here. On this particular kata, I haven't made visible data on the sample tests because the population is quite cumbersome, heavily using Ruby, so I thought that it could scare users rather than help :) Regarding table definition - I always make it directly in the kata description. So thus do not display it because it will be a repetition.

      Cheers!

      Question marked resolved by bornForThis 2 years ago