aboutsummaryrefslogtreecommitdiffhomepage
path: root/ruby/tests/generated_code_test.rb
Commit message (Collapse)AuthorAge
* Adopt ruby_package in ruby generated code. (#4627)Gravatar Paul Yang2018-05-17
| | | | | | * Adopt ruby_package in ruby generated code. * Add test for ruby_package
* Added unit test for PascalCasing package names in Ruby.Gravatar Josh Haberman2016-07-25
|
* Ruby: generated foo.proto -> foo_pb.rb instead of foo.rb.Gravatar Josh Haberman2016-07-25
| | | | | This brings us more into line with other langauges, and makes it more obvious when we are requiring protobuf generated code.
* Two tests for Ruby code generator:Gravatar Chris Fallin2015-01-14
- A golden-file test that ensures protoc produces known-valid output. - A Ruby test that loads that golden file and ensures it actually works with the extension. This split strategy allows us to test end-to-end without needing to integrate the Ruby gem build system and the protoc build system. This is desirable because we do not want a gem build/install to depend on building protoc, and we do not want building protoc to depend on building and testing the gem.