Accueil Explorer Aide
Connexion
carto
/
protobuf
2
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki
Aborescence: 15b60bccf8
Branches Tags
protobuf
/
conformance
Joshua Haberman cad6a51a30 Merge pull request #2819 from haberman/pythonexcept il y a 8 ans
..
third_party a0cecfd31a Make conformance tests build for C++ and Java. il y a 10 ans
ConformanceJava.java f1ce60e7b4 Factored Conformance and Benchmark test messages into shared test schema. (#1971) il y a 9 ans
ConformanceJavaLite.java 3808d091f8 Fix spelling in strings and comments il y a 9 ans
Makefile.am 39756643df Add conformance test for php (#2655) il y a 8 ans
README.md 35a1cc7a7c Added first version of conformance tests. il y a 10 ans
conformance.proto f1ce60e7b4 Factored Conformance and Benchmark test messages into shared test schema. (#1971) il y a 9 ans
conformance_cpp.cc e3da722b66 Fix #include in cc files il y a 9 ans
conformance_objc.m f1ce60e7b4 Factored Conformance and Benchmark test messages into shared test schema. (#1971) il y a 9 ans
conformance_php.php dd8d5f57d7 Rename encode/decode to serializeToString/mergeFromString (#2795) il y a 8 ans
conformance_python.py f1ce60e7b4 Factored Conformance and Benchmark test messages into shared test schema. (#1971) il y a 9 ans
conformance_ruby.rb f1ce60e7b4 Factored Conformance and Benchmark test messages into shared test schema. (#1971) il y a 9 ans
conformance_test.cc ffa71f8007 A few more cases for binary conformance tests. (#2500) il y a 8 ans
conformance_test.h 2ff42dcf2c Added conformance testing for binary primitive types. (#2491) il y a 9 ans
conformance_test_runner.cc cc8ca5b6a5 Integrate internal changes il y a 9 ans
failure_list_cpp.txt 5a76e633ea Integrated internal changes from Google il y a 9 ans
failure_list_csharp.txt 1f077a0183 Update conformance failure lists. il y a 9 ans
failure_list_java.txt a41090ee6b Updated failure_list_java.txt for Java conformance test il y a 9 ans
failure_list_objc.txt ca5b7751e5 Record zero for "has" for proto3 if in a oneof. il y a 9 ans
failure_list_php.txt 39756643df Add conformance test for php (#2655) il y a 8 ans
failure_list_php_c.txt cba04b19e8 Implement json encoding decoding for php. (#2682) il y a 8 ans
failure_list_python-post26.txt ea909a57e4 Updated C#'s failure list, and added missing file. il y a 9 ans
failure_list_python.txt 5a76e633ea Integrated internal changes from Google il y a 9 ans
failure_list_python_cpp.txt 5a76e633ea Integrated internal changes from Google il y a 9 ans
failure_list_ruby.txt 1f077a0183 Update conformance failure lists. il y a 9 ans
update_failure_list.py 3e6245e5d7 update_failure_list.py: fixed Python "raise" statement. il y a 8 ans

README.md

Protocol Buffers - Google's data interchange format

Build Status

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

Then to run the tests against the C++ implementation, run:

$ cd conformance && make test_cpp

More tests and languages will be added soon!

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