Google Git
Sign in
flutter / third_party / protobuf / c51a8a2c10d3e08492b31e9b006d348bd2c8f916 / . / conformance
tree: d3c68f73c8c0ebaf54c8a44ab43711c076f7f99d [path history] [tgz]
  1. third_party/
  2. autoload.php
  3. binary_json_conformance_suite.cc
  4. binary_json_conformance_suite.h
  5. conformance.proto
  6. conformance_cpp.cc
  7. conformance_nodejs.js
  8. conformance_objc.m
  9. conformance_php.php
  10. conformance_python.py
  11. conformance_ruby.rb
  12. conformance_test.cc
  13. conformance_test.h
  14. conformance_test_main.cc
  15. conformance_test_runner.cc
  16. conformance_test_runner.sh
  17. ConformanceJava.java
  18. ConformanceJavaLite.java
  19. failure_list_cpp.txt
  20. failure_list_csharp.txt
  21. failure_list_java.txt
  22. failure_list_java_lite.txt
  23. failure_list_jruby.txt
  24. failure_list_js.txt
  25. failure_list_objc.txt
  26. failure_list_php.txt
  27. failure_list_php_c.txt
  28. failure_list_python-post26.txt
  29. failure_list_python.txt
  30. failure_list_python_cpp.txt
  31. failure_list_ruby.txt
  32. Makefile.am
  33. README.md
  34. text_format_conformance_suite.cc
  35. text_format_conformance_suite.h
  36. text_format_failure_list_cpp.txt
  37. text_format_failure_list_csharp.txt
  38. text_format_failure_list_java.txt
  39. text_format_failure_list_java_lite.txt
  40. text_format_failure_list_jruby.txt
  41. text_format_failure_list_php.txt
  42. text_format_failure_list_python.txt
  43. text_format_failure_list_python_2.7.txt
  44. text_format_failure_list_python_cpp.txt
  45. text_format_failure_list_python_cpp_2.7.txt
  46. text_format_failure_list_ruby.txt
  47. update_failure_list.py
conformance/README.md

Protocol Buffers - Google's data interchange format

Copyright 2008 Google Inc.

This directory contains conformance tests for testing completeness and correctness of Protocol Buffers implementations. These tests are designed to be easy to run against any Protocol Buffers implementation.

This directory contains the tester process conformance-test, which contains all of the tests themselves. Then separate programs written in whatever language you want to test communicate with the tester program over a pipe.

Before running any of these tests, make sure you run make in the base directory to build protoc, since all the tests depend on it.

$ make

Running the tests for C++

To run the tests against the C++ implementation, run:

$ cd conformance && make test_cpp

Running the tests for JavaScript (Node.js)

To run the JavaScript tests against Node.js, make sure you have “node” on your path and then run:

$ cd conformance && make test_nodejs

Running the tests for Ruby (MRI)

To run the Ruby tests against MRI, first build the C extension:

$ cd ruby && rake

Then run the tests like so:

$ cd conformance && make test_ruby

Running the tests for other languages

Most of the languages in the Protobuf source tree are set up to run conformance tests. However some of them are more tricky to set up properly. See tests.sh in the base of the repository to see how Travis runs the tests.

Testing other Protocol Buffer implementations

To run these tests against a new Protocol Buffers implementation, write a program in your language that uses the protobuf implementation you want to test. This program should implement the testing protocol defined in conformance.proto. This is designed to be as easy as possible: the C++ version is only 150 lines and is a good example for what this program should look like (see conformance_cpp.cc). The program only needs to be able to read from stdin and write to stdout.

Portability

Note that the test runner currently does not work on Windows. Patches to fix this are welcome! (But please get in touch first to settle on a general implementation strategy).