protobuf/conformance
Sydney Acksman 15fab9109d Bump target frameworks of C# programs from netcoreapp1.0 to netcoreapp2.1 (#5838)
* Bump target frameworks from netcoreapp1.0 to netcoreapp2.2.
Move global.json up to root of repo, change SDK ver to 2.2.100
Change .net core sdk in dockerfile for kokoro to ver 2.2.100

* Re-add curl install

* Change all exe target to 2.1

* Fix incorrect versions in global.json and Dockerfile

* Downgrade version to 2.1 to match exe targets

* introduce separate testing Dockerfile for C#

* revert changes to the shared Dockerfile

* use netcoreapp2.1 for C# conformance tests

* use language specific dockerfile for testing C#

* Edit compatibility tests script to use parameters instead of file copies

* install dotnet SDK on windows before running the tests

* update csharp_EXTRA_DIST
2019-03-11 13:03:58 -07:00
..
third_party/jsoncpp delete all duplicate empty blanks (#5758) 2019-02-20 19:28:50 -08: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 down integration from internal 2019-02-22 18:13:33 +08:00
binary_json_conformance_suite.h Down-integrate internal changes (#5467) 2018-12-14 16:05:03 -08:00
conformance_cpp.cc Down-integrate internal changes to github. (#5566) 2019-01-11 11:40:52 -08:00
conformance_nodejs.js fix conformance test for text format 2019-02-26 13:46:30 -08:00
conformance_objc.m [ObjC] add support for the TextFormat constants. 2019-01-14 11:03:16 -05:00
conformance_php.php fix conformance test for text format 2019-02-26 13:46:30 -08:00
conformance_python.py down integration from internal 2019-02-22 18:13:33 +08:00
conformance_ruby.rb fix conformance test for text format 2019-02-26 13:46:30 -08:00
conformance_test_main.cc down integration from internal 2019-02-22 18:13:33 +08:00
conformance_test_runner.cc down integration from internal 2019-02-22 18:13:33 +08:00
conformance_test.cc down integration from internal 2019-02-22 18:13:33 +08:00
conformance_test.h down integration from internal 2019-02-22 18:13:33 +08:00
conformance.proto Down-integrate internal changes to github. (#5575) 2019-01-13 17:40:58 -08:00
ConformanceJava.java Merge branch 'master' into integration 2019-02-24 17:17:17 -08:00
ConformanceJavaLite.java Fix spelling in strings and comments 2016-07-03 15:26:04 +03:00
failure_list_cpp.txt Down-integrate internal changes to github. (#5555) 2019-01-08 15:06:30 -08:00
failure_list_csharp.txt Down-integrate from google3. 2018-08-08 17:00:41 -07:00
failure_list_java.txt Down-integrate from google3. 2018-08-08 17:00:41 -07:00
failure_list_js.txt Fix JS conformance tests 2017-10-18 15:09:21 -07:00
failure_list_objc.txt Properly error on a tag with field number zero. 2017-06-06 10:14:41 -04:00
failure_list_php_c.txt Default values should also be serialized for json map key/value (#5643) 2019-01-28 19:30:10 +00:00
failure_list_php_zts_c.txt Add json encode/decode for php. (#3226) 2017-06-30 12:14:09 -07:00
failure_list_php.txt Convert integer to string if field is string field in json 2019-01-28 20:57:51 +00:00
failure_list_python_cpp.txt down integration from internal 2019-02-22 18:13:33 +08:00
failure_list_python-post26.txt Down-integrate from google3. 2018-08-08 17:00:41 -07:00
failure_list_python.txt down integration from internal 2019-02-22 18:13:33 +08:00
failure_list_ruby_mac.txt Fix ruby continuous tests (#5853) 2019-03-07 17:16:31 -08:00
failure_list_ruby.txt Fix ruby continuous tests (#5853) 2019-03-07 17:16:31 -08:00
Makefile.am Bump target frameworks of C# programs from netcoreapp1.0 to netcoreapp2.1 (#5838) 2019-03-11 13:03:58 -07:00
README.md Replace repo links. 2018-08-22 11:55:30 -07:00
text_format_conformance_suite.cc Down integrate to Github (#5839) 2019-03-06 12:39:12 -08:00
text_format_conformance_suite.h down integration from internal 2019-02-22 18:13:33 +08:00
text_format_failure_list_python.txt Down integrate to Github (#5839) 2019-03-06 12:39:12 -08: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 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).