package protobuf_unittest

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service TestService

unittest.proto:624

message Data

unittest_couchdb.proto:10

enum ForeignEnum

unittest.proto:174

Used in: TestAllTypes, TestCamelCaseFieldNames, TestDynamicExtensions, TestPackedTypes, TestUnpackedTypes

message ForeignMessage

unittest.proto:170

Define these after TestAllTypes to make sure the compiler can handle that.

Used in: TestAllTypes, TestCamelCaseFieldNames, TestDynamicExtensions, TestNestedMessageHasBits.NestedMessage

message Holder

unittest_multi_nested.proto:20

Used in: Inner

message Inner

unittest_multi_nested.proto:15

Used in: Outer

message OneBytes

unittest.proto:515

message OneString

unittest.proto:511

Test String and Bytes: string is for valid UTF-8 strings

message OptionalGroup_extension

unittest.proto:202

message Outer

unittest_multi_nested.proto:10

message RepeatedGroup_extension

unittest.proto:236

message SparseEnumMessage

unittest.proto:506

message TestAllExtensions

unittest.proto:180

(message has no fields)

message TestAllTypes

unittest.proto:60

This proto includes every type of field in both singular and repeated forms.

enum TestAllTypes.NestedEnum

unittest.proto:68

Used in: TestAllTypes

message TestAllTypes.NestedMessage

unittest.proto:61

Used in: TestAllTypes, TestForeignNested

message TestAllTypes.OptionalGroup

unittest.proto:91

Used in: TestAllTypes

message TestAllTypes.RepeatedGroup

unittest.proto:123

Used in: TestAllTypes

message TestCamelCaseFieldNames

unittest.proto:434

Test message with CamelCase field names. This violates Protocol Buffer standard style.

message TestDeprecatedFields

unittest.proto:164

message TestDupFieldNumber

unittest.proto:394

Test that groups have disjoint field numbers from their siblings and parents. This is NOT possible in proto1; only proto2. When attempting to compile with proto1, this will emit an error; so we only include it in protobuf_unittest_proto.

NO_PROTO1

message TestDupFieldNumber.Bar

unittest.proto:397

Used in: TestDupFieldNumber

message TestDupFieldNumber.Foo

unittest.proto:396

Used in: TestDupFieldNumber

message TestDynamicExtensions

unittest.proto:581

Used by ExtensionSetTest/DynamicExtensions. The test actually builds a set of extensions to TestAllExtensions dynamically, based on the fields of this message type.

enum TestDynamicExtensions.DynamicEnumType

unittest.proto:582

Used in: TestDynamicExtensions

message TestDynamicExtensions.DynamicMessageType

unittest.proto:587

Used in: TestDynamicExtensions

message TestEmptyMessage

unittest.proto:352

TestEmptyMessage is used to test unknown field support.

(message has no fields)

message TestEmptyMessageWithExtensions

unittest.proto:357

Like above, but declare all field numbers as potential extensions. No actual extensions should ever be defined for this type.

(message has no fields)

enum TestEnumWithDupValue

unittest.proto:412

Test an enum that has multiple values with the same number.

message TestExtremeDefaultValues

unittest.proto:468

message TestFieldOrderings

unittest.proto:453

We list fields out of order, to ensure that we're using field number and not field index to determine serialization order.

message TestForeignNested

unittest.proto:347

Test that we can use NestedMessage from outside TestAllTypes.

message TestMultipleExtensionRanges

unittest.proto:361

(message has no fields)

message TestMutualRecursionA

unittest.proto:381

Test that mutual recursion works.

Used in: TestMutualRecursionB

message TestMutualRecursionB

unittest.proto:385

Used in: TestMutualRecursionA

message TestNestedExtension

unittest.proto:282

(message has no fields)

message TestNestedMessageHasBits

unittest.proto:402

Needed for a Python test.

message TestNestedMessageHasBits.NestedMessage

unittest.proto:403

Used in: TestNestedMessageHasBits

message TestNullField

unittest.proto:633

message TestPackedExtensions

unittest.proto:557

(message has no fields)

message TestPackedTypes

unittest.proto:521

message TestReallyLargeTagNumber

unittest.proto:368

Test that really large tag numbers don't break anything.

message TestRecursiveMessage

unittest.proto:375

message TestRepeatedScalarDifferentTagSizes

unittest.proto:602

message TestRequired

unittest.proto:295

We have separate messages for testing required fields because it's annoying to have to fill in required fields in TestProto in order to do anything with it. Note that we don't need to test every type of required filed because the code output is basically identical to optional fields for all types.

Used in: TestRequiredForeign

message TestRequiredForeign

unittest.proto:340

enum TestSparseEnum

unittest.proto:422

Test an enum with large, unordered values.

Used in: SparseEnumMessage

message TestUnpackedTypes

unittest.proto:540

A message with the same fields as TestPackedTypes, but without packing. Used to test packed <-> unpacked wire compatibility.