Impliment new template based generator

.github/workflows/generator-tests.yml

@@ -0,0 +1,32 @@
+name: GeneratorTests
+
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test-generator-templates:
+    name: Test Generator
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@52753b7da854d5c07df37391a986c76ab4615999
+        with:
+          ruby-version: "3.3"
+          bundler-cache: true
+        run: ruby ./bin/generator.rb --verify
+  test-generator:
+    name: Check Generator Templates
+    runs-on: ubuntu-22.04
+    container:
+      image: crystallang/crystal
+    steps:
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@52753b7da854d5c07df37391a986c76ab4615999
+        with:
+          ruby-version: "3.3"
+          bundler-cache: true
+        run: rake test:generator

Gemfile

@@ -8,3 +8,4 @@ gem 'rubocop-minitest', require: false
 gem 'rubocop-rake', require: false
 gem 'simplecov', require: false
 gem 'racc', require: false
+gem 'toml-rb', require: false

Gemfile.lock

@@ -2,6 +2,7 @@ GEM
   remote: https://rubygems.org/
   specs:
     ast (2.4.2)
+    citrus (3.0.2)
     docile (1.4.0)
     json (2.7.2)
     minitest (5.22.3)
@@ -41,6 +42,10 @@ GEM
       simplecov_json_formatter (~> 0.1)
     simplecov-html (0.12.3)
     simplecov_json_formatter (0.1.4)
+    strscan (3.1.0)
+    toml-rb (3.0.1)
+      citrus (~> 3.0, > 3.0)
+      racc (~> 1.7)
     unicode-display_width (2.5.0)
 
 PLATFORMS
@@ -55,6 +60,7 @@ DEPENDENCIES
   rubocop-minitest
   rubocop-rake
   simplecov
+  toml-rb
 
 BUNDLED WITH
    2.5.7

Rakefile

@@ -25,5 +25,10 @@ namespace :test do
     task.pattern = 'test/**/*_test.rb'
   end
 
+  Rake::TestTask.new :generator do |task|
+    task.options = flags
+    task.pattern = 'generatorv2/test/**/*_test.rb'
+  end
+
   ExerciseTestTasks.new options: flags
 end

bin/generate.rb

@@ -0,0 +1,41 @@
+require 'optparse'
+require 'tempfile'
+require_relative '../generatorv2/lib/generator'
+
+parser = OptionParser.new
+
+parser.on('-v', '--version', 'Print the version') do
+  puts '0.1.0'
+end
+
+parser.on('-h', '--help', 'Prints help') do
+  puts parser
+end
+
+parser.on('-a', '--all', 'Generate all exercises') do
+  exercises = Dir.entries('./exercises/practice').select { |f| File.directory? File.join('./exercises/practice', f) }
+  exercises.each do |exercise|
+    if File.exist?("./exercises/practice/#{exercise}/.meta/test_template.erb")
+      Generator.new(exercise).generate
+    end
+  end
+end
+
+parser.on('--verify', 'Verify all exercises') do
+  exercises = Dir.entries('./exercises/practice').select { |f| File.directory? File.join('./exercises/practice', f) }
+  exercises.each do |exercise|
+    if File.exist?("./exercises/practice/#{exercise}/.meta/test_template.erb")
+      current_code = File.read("./exercises/practice/#{exercise}/#{exercise}_test.rb")
+      f = Tempfile.create
+      Generator.new(exercise).generate(f.path)
+      generated_code = f.read
+      raise RuntimeError.new("The result generated for: #{exercise}, doesnt match the current file") if current_code != generated_code
+    end
+  end
+end
+
+parser.on('-e', '--exercise EXERCISE', 'The exercise to generate') do |exercise|
+  Generator.new(exercise).generate
+end
+
+parser.parse!

exercises/practice/acronym/.meta/test_template.erb

@@ -0,0 +1,13 @@
+require 'minitest/autorun'
+require_relative 'acronym'
+
+class AcronymTest < Minitest::Test
+<% json["cases"].each do |cases| %>
+    def test_<%= underscore(cases["description"]) %>
+        <%= status() %> 
+        assert_equal '<%= cases["expected"] %>', <%= camel_case(json["exercise"]) %>.<%= underscore(cases["property"]) %>('<%= cases["input"]["phrase"] %>')
+    end
+<% end %>
+end
+
+

exercises/practice/acronym/acronym_test.rb

@@ -4,37 +4,37 @@
 class AcronymTest < Minitest::Test
   def test_basic
     # skip
-    assert_equal "PNG", Acronym.abbreviate('Portable Network Graphics')
+    assert_equal 'PNG', Acronym.abbreviate('Portable Network Graphics')
   end
 
   def test_lowercase_words
     skip
-    assert_equal "ROR", Acronym.abbreviate('Ruby on Rails')
+    assert_equal 'ROR', Acronym.abbreviate('Ruby on Rails')
   end
 
   def test_punctuation
     skip
-    assert_equal "FIFO", Acronym.abbreviate('First In, First Out')
+    assert_equal 'FIFO', Acronym.abbreviate('First In, First Out')
   end
 
   def test_all_caps_word
     skip
-    assert_equal "GIMP", Acronym.abbreviate('GNU Image Manipulation Program')
+    assert_equal 'GIMP', Acronym.abbreviate('GNU Image Manipulation Program')
   end
 
   def test_punctuation_without_whitespace
     skip
-    assert_equal "CMOS", Acronym.abbreviate('Complementary metal-oxide semiconductor')
+    assert_equal 'CMOS', Acronym.abbreviate('Complementary metal-oxide semiconductor')
   end
 
   def test_very_long_abbreviation
     skip
-    assert_equal "ROTFLSHTMDCOALM",
+    assert_equal 'ROTFLSHTMDCOALM',
       Acronym.abbreviate('Rolling On The Floor Laughing So Hard That My Dogs Came Over And Licked Me')
   end
 
   def test_consecutive_delimiters
     skip
-    assert_equal "SIMUFTA", Acronym.abbreviate('Something - I made up from thin air')
+    assert_equal 'SIMUFTA', Acronym.abbreviate('Something - I made up from thin air')
   end
 end

generatorv2/README.md

@@ -0,0 +1,139 @@
+# Generator
+
+Last Updated: 2024/11/9
+
+The generator is a powerful tool that can be used to generate tests for exercises based on the canonical data.
+The generator is written in Ruby and is located in the `bin` directory.
+
+## How to use the generator
+
+### Things to do before running the generator
+
+Before running the generator you have to make sure a couple of files are in place.
+
+1. `tests.toml` file
+
+It is located under the `.meta` folder for each exercise.
+The toml file is used to configure which exercises are generated and which are not.
+Since the generator grabs all the data from the canonical data, so does this enable new tests that won't automatically be merged in.
+Instead so does new tests have to be added to the toml file before they show up in the test file.
+
+If there is a test that isn't needed or something that doesn't fit Ruby you can remove it from the toml file.
+By writing after the test name `include = false` and it will be skipped when generating the test file.
+
+2. `config.json` file, located in the root of the track
+
+The generator makes sure that the exercise is in the config.json so you need to add it there before running the generator.
+
+3. `spec` directory
+
+The generator will create a spec file for each exercise, so you need to make sure that the spec directory is in place.
+Although there don't have to be any files in the directory, since the script will create one for you.
+If it is a file already so will the generator overwrite it.
+
+#### Things to note
+
+The script which grabs info from the toml file is quite sensitive, writing the toml file in an incorrect way can brick the generator.
+
+Here are some examples of how you should **NOT** work with the toml file.
+
+Make sure that the uuid is the only thing inside of `[uuid]`, if there is, for example, an extra space so would that break it.
+Here is an example
+
+```toml
+# This would break it since it is an extra space between uuid and `]`
+[1e22cceb-c5e4-4562-9afe-aef07ad1eaf4 ]
+# This would break it since it is an extra space between uuid and `[`
+[ 1e22cceb-c5e4-4562-9afe-aef07ad1eaf4]
+```
+
+The script won't care if you write `include = true` since if it sees the uuid it will always take it as long as `include = false` is not written.
+The script will not work if anything is misspelled, although the part which gets `include = false` doesn't care if it gets an extra space or not.
+
+**NOTE:**
+You are also **NOT** allowed to write `include = false` more than once after each uuid.
+Since that can lead to errors in the generator.
+
+Bad way:
+
+```toml
+[1e22cceb-c5e4-4562-9afe-aef07ad1eaf4]
+description = "basic"
+include = false
+include = false
+```
+
+Good way:
+
+```toml
+[1e22cceb-c5e4-4562-9afe-aef07ad1eaf4]
+description = "basic"
+include = false
+```
+
+### Template
+
+The generator uses a template file to generate the test file.
+The template is located under the `.meta` for each exercise.
+
+This template has to be manually written for each exercise.
+The goal although is to make it so that you only have to write the template once and then it will be able to be used to generate new tests.
+
+The template file is written in [Embedded Ruby(ERB)][erb].
+ERB enables you to write Ruby code inside of the template file.
+It also means that the templates can be highly customizable since you can write any Ruby code you want.
+
+When writing the template file it is recommended to look at already existing template files to get a better understanding of how it works.
+The template is getting a slightly modified version of the canonical data, so you can check out the [canonical data][canonical data] to see the data structure.
+The modification is that the cases which are not included in the toml file will be removed from the data structure.
+
+When writing the template so is it a special tool that can help with giving `# skip` and `skip` tags for tests.
+You simply have to call the `status` method.
+It will return either `# skip` or `skip` depending on if it is the first test case or not.
+
+Here is an example:
+
+```
+<%= status()%>
+<%= status()%>
+<%= status()%>
+```
+
+result:
+
+```
+# skip
+skip
+skip
+```
+
+### The Test Generator
+
+If all the earlier steps are done so can you run the generator.
+To run the generator you need to have a working Ruby installation and installed all gems in the Gemfile.
+The generator is located in the `bin` directory and is called `generator.rb`.
+
+To run the generator so do you have to be in the root directory and run the following command:
+
+```shell
+ruby ./bin/generator.rb -e <exercise_slug>
+```
+
+Where `<exercise_slug>` is the same name as the slug name which is located in the `config.json` file.
+
+For more commands so can you run the following command:
+
+```shell
+ruby ./bin/generator.rb --help
+```
+
+### Errors and warnings
+
+The generator will give you errors and warnings if something is wrong.
+That includes if the exercise is not in the `config.json` file, if the exercise is not in the toml file, or if the template file is missing.
+Also if it has a problem getting the `canonical-data.json` file so will it give you an error.
+The generator also uses a formatter which will give you errors if the generated file is not formatted correctly.
+The file will still be generated even if formatter gives errors, therefore can you check the file and see what is wrong and fix it in the template.
+
+[erb]: https://docs.ruby-lang.org/en/master/ERB.html
+[canonical data]: https://github.com/exercism/problem-specifications