describe FastlaneCI do
  describe "docs" do
    Dir["features/*"].each do |feature_directory|
      next unless File.directory?(feature_directory)
      it "#{feature_directory} has a README.md" do
        readme_path = File.join(feature_directory, "README.md")
        expect(File.exist?(readme_path)).to eq(true), "Every directory in the `feature` area must have a README.md describing the scope and responsibilities of the classes (#{feature_directory})"
      end
    end

    Dir["services/*"].each do |service_directory|
      next unless File.directory?(service_directory)
      it "#{service_directory} has a README.md" do
        readme_path = File.join(service_directory, "README.md")
        expect(File.exist?(readme_path)).to eq(true), "Every directory in the `feature` area must have a README.md describing the scope and responsibilities of the classes (#{service_directory})"
      end
    end
  end
end

Add tests to ensure each feature and service directory has a README.md
Add tests to ensure each feature and service directory has a README.md

Just like how we enforce class based comments for each class using rubocop, we should build fastlane.ci with a good documentation base. Having a README.md will make it easy for everyone working on this to see what's going on when they use the code locally, but also makes it a ton easier when using GitHub.com to browse through source code 👍

It's always good to enforce those practices, as it's much easier to add them as we build the system, vs spending a lot of time later on on adding them

This currently causes 13 failures, please append commits to this PR to add the missing documentation for the classes you have enough knowledge of to describe what they're responsible for
