protobuf/conformance
Adam Cozzette 860f8ad171
Remove the JavaScript implementation (#9874)
This implementation is about to be split out into a separate Git repo.
2022-04-28 12:08:26 -07:00
..
third_party/jsoncpp Sync from Piper @327110949 2020-08-17 15:26:13 -07:00
autoload.php Fix php well known type conformance tests (#3828) (#3840) 2017-11-04 09:33:56 -07:00
binary_json_conformance_suite.cc Sync from Piper @439400376 2022-04-04 13:42:37 -07:00
binary_json_conformance_suite.h Sync from Piper @373820256 2021-05-14 17:50:31 +00:00
conformance_cpp.cc Fix conformance_cpp 2021-03-10 10:05:31 +01:00
conformance_nodejs.js Sync from Piper @429333699 2022-02-17 09:53:51 -08:00
conformance_objc.m Down integrate to GitHub 2019-08-22 17:33:01 -07:00
conformance_php.php Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
conformance_python.py Fixing more tests 2022-02-02 22:21:04 +00:00
conformance_ruby.rb Ported Ruby extension to upb_msg (#8184) 2021-01-13 12:16:25 -08:00
conformance_test_main.cc down integration from internal 2019-02-22 18:13:33 +08:00
conformance_test_runner.cc Sync from Piper @427369078 2022-02-08 20:53:31 -08:00
conformance_test_runner.sh Bazel powered Java testing (#8506) 2021-04-20 11:36:32 -07:00
conformance_test.cc Sync from Piper @427369078 2022-02-08 20:53:31 -08:00
conformance_test.h Sync from Piper @427369078 2022-02-08 20:53:31 -08:00
conformance.proto Sync from Piper @395706834 2021-09-09 08:21:42 -07:00
ConformanceJava.java more descriptive error messages and exceptions (#9868) 2022-04-27 17:02:01 +00:00
ConformanceJavaLite.java Sync from Piper @368734211 2021-04-15 15:53:17 -07:00
failure_list_cpp.txt Sync from Piper @310858019 2020-05-11 00:12:20 -07:00
failure_list_csharp.txt Sync from Piper @368903491 2021-04-16 12:59:54 -07:00
failure_list_java_lite.txt Sync from Piper @368903491 2021-04-16 12:59:54 -07:00
failure_list_java.txt Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
failure_list_jruby.txt Update JRuby to leverage pure-Ruby DSL. 2021-10-03 18:25:43 -04:00
failure_list_js.txt Fixed JavaScript conformance test and failure list. 2022-02-08 23:06:32 -08:00
failure_list_objc.txt Fix enum writing. 2019-08-26 17:17:32 -04:00
failure_list_php_c.txt Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
failure_list_php.txt Sync from Piper @368903491 2021-04-16 12:59:54 -07:00
failure_list_python_cpp.txt Sync from Piper @316511779 2020-06-15 11:48:47 -07:00
failure_list_python-post26.txt Down-integrate from google3. 2018-08-08 17:00:41 -07:00
failure_list_python.txt Sync from Piper @316511779 2020-06-15 11:48:47 -07:00
failure_list_ruby.txt Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
Makefile.am Remove the JavaScript implementation (#9874) 2022-04-28 12:08:26 -07:00
README.md more descriptive error messages and exceptions (#9868) 2022-04-27 17:02:01 +00:00
text_format_conformance_suite.cc Sync from Piper @364389596 2021-03-22 13:05:55 -07:00
text_format_conformance_suite.h Sync from Piper @373820256 2021-05-14 17:50:31 +00:00
text_format_failure_list_cpp.txt Sync from Piper @334206209 2020-09-28 11:54:54 -07:00
text_format_failure_list_csharp.txt Update conformance test failures 2019-03-20 14:43:42 -07:00
text_format_failure_list_java_lite.txt Sync from Piper @368903491 2021-04-16 12:59:54 -07:00
text_format_failure_list_java.txt Sync from Piper @395706834 2021-09-09 08:21:42 -07:00
text_format_failure_list_jruby.txt Set up testing configuration for jruby 2020-12-11 16:02:41 -08:00
text_format_failure_list_php.txt Update conformance test failures 2019-03-20 14:43:42 -07:00
text_format_failure_list_python_cpp.txt Sync from Piper @334206209 2020-09-28 11:54:54 -07:00
text_format_failure_list_python.txt Sync from Piper @334206209 2020-09-28 11:54:54 -07:00
text_format_failure_list_ruby.txt Update conformance test failures 2019-03-20 14:43:42 -07:00
update_failure_list.py file() was removed in Python 3, use open() instead 2017-08-18 01:04:17 +02:00

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 Kokoro 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).