• Home
Name
Date
Size
#Lines
LOC

..--

third_party/jsoncpp/12-May-2024-7,2695,161

ConformanceJava.javaD12-May-202414.6 KiB396324

ConformanceJavaLite.javaD12-May-20245.1 KiB155100

Makefile.amD12-May-202422.5 KiB376257

README.mdD12-May-20242.5 KiB7249

autoload.phpD12-May-2024752 2217

binary_json_conformance_suite.ccD12-May-2024117.5 KiB3,2362,892

binary_json_conformance_suite.hD12-May-20246.7 KiB142102

conformance.protoD12-May-20247.2 KiB177155

conformance_cpp.ccD12-May-20248.5 KiB264190

conformance_nodejs.jsD12-May-20246 KiB187125

conformance_objc.mD12-May-20247.2 KiB216186

conformance_php.phpD12-May-20244.2 KiB121104

conformance_python.pyD12-May-20249 KiB214145

conformance_ruby.rbD12-May-20244.4 KiB13883

conformance_test.ccD12-May-202415.8 KiB459373

conformance_test.hD12-May-202411.9 KiB324162

conformance_test_main.ccD12-May-20242 KiB419

conformance_test_runner.ccD12-May-202411.5 KiB346228

failure_list_cpp.txtD12-May-20242 KiB3836

failure_list_csharp.txtD12-May-2024182 43

failure_list_java.txtD12-May-20242.7 KiB4947

failure_list_js.txtD12-May-202410.6 KiB116114

failure_list_objc.txtD12-May-2024139 32

failure_list_php.txtD12-May-20241.6 KiB2928

failure_list_php_c.txtD12-May-2024117 32

failure_list_php_c_32.txtD12-May-2024117 32

failure_list_python-post26.txtD12-May-202486 32

failure_list_python.txtD12-May-20240

failure_list_python_cpp.txtD12-May-2024409 98

failure_list_ruby.txtD12-May-20248.8 KiB112111

text_format_conformance_suite.ccD12-May-202414.6 KiB380301

text_format_conformance_suite.hD12-May-20243.2 KiB7033

text_format_failure_list_csharp.txtD12-May-2024608 98

text_format_failure_list_java.txtD12-May-2024416 76

text_format_failure_list_php.txtD12-May-2024608 98

text_format_failure_list_python.txtD12-May-2024253 65

text_format_failure_list_ruby.txtD12-May-2024608 98

update_failure_list.pyD12-May-20242.8 KiB7432

README.md

1Protocol Buffers - Google's data interchange format
2===================================================
3
4Copyright 2008 Google Inc.
5
6This directory contains conformance tests for testing completeness and
7correctness of Protocol Buffers implementations.  These tests are designed
8to be easy to run against any Protocol Buffers implementation.
9
10This directory contains the tester process `conformance-test`, which
11contains all of the tests themselves.  Then separate programs written
12in whatever language you want to test communicate with the tester
13program over a pipe.
14
15Before running any of these tests, make sure you run `make` in the base
16directory to build `protoc`, since all the tests depend on it.
17
18    $ make
19
20Running the tests for C++
21-------------------------
22
23To run the tests against the C++ implementation, run:
24
25    $ cd conformance && make test_cpp
26
27Running the tests for JavaScript (Node.js)
28------------------------------------------
29
30To run the JavaScript tests against Node.js, make sure you have "node"
31on your path and then run:
32
33    $ cd conformance && make test_nodejs
34
35Running the tests for Ruby (MRI)
36--------------------------------
37
38To run the Ruby tests against MRI, first build the C extension:
39
40    $ cd ruby && rake
41
42Then run the tests like so:
43
44    $ cd conformance && make test_ruby
45
46Running the tests for other languages
47-------------------------------------
48
49Most of the languages in the Protobuf source tree are set up to run
50conformance tests.  However some of them are more tricky to set up
51properly.  See `tests.sh` in the base of the repository to see how
52Travis runs the tests.
53
54Testing other Protocol Buffer implementations
55---------------------------------------------
56
57To run these tests against a new Protocol Buffers implementation, write a
58program in your language that uses the protobuf implementation you want
59to test.  This program should implement the testing protocol defined in
60[conformance.proto](https://github.com/protocolbuffers/protobuf/blob/master/conformance/conformance.proto).
61This is designed to be as easy as possible: the C++ version is only
62150 lines and is a good example for what this program should look like
63(see [conformance_cpp.cc](https://github.com/protocolbuffers/protobuf/blob/master/conformance/conformance_cpp.cc)).
64The program only needs to be able to read from stdin and write to stdout.
65
66Portability
67-----------
68
69Note that the test runner currently does not work on Windows.  Patches
70to fix this are welcome!  (But please get in touch first to settle on
71a general implementation strategy).
72