pyCraft/tests
joo 969419da3f Fix: non-monotonic protocol versions are not correctly handled
After 1.16.3, Mojang started publishing snapshot, pre-release and release
candidate versions of Minecraft with protocol version numbers of the form
`(1 << 30) | n' where 'n' is a small non-negative integer increasing with each
such version; the release versions continued to use the old format. For
example, these are the last 8 published Minecraft versions as of this commit:

release           1.16.3      uses protocol version 753
pre-release       1.16.4-pre1 uses protocol version 1073741825 == (1 << 30) | 1
pre-release       1.16.4-pre2 uses protocol version 1073741826 == (1 << 30) | 2
release candidate 1.16.4-rc1  uses protocol version 1073741827 == (1 << 30) | 3
release           1.16.4      uses protocol version 754
snapshot          20w45a      uses protocol version 1073741829 == (1 << 30) | 5
snapshot          20w46a      uses protocol version 1073741830 == (1 << 30) | 6
snapshot          20w48a      uses protocol version 1073741831 == (1 << 30) | 7

This means that protocol versions no longer increase monotonically with respect
to publication history, a property that was assumed to hold in much of
pyCraft's code relating to support of multiple protocol versions. This commit
rectifies the issue by replacing any comparison of protocol versions by their
numerical value with a comparison based on their publication time.

Newly defined is the dictionary `minecraft.PROTOCOL_VERSION_INDICES', which
maps each known protocol version to its index in the protocol chronology. As
such, the bound method `minecraft.PROTOCOL_VERSION_INDICES.get` can be used as
a key function for the built-in `sorted`, `min` and `max` functions to collate
protocol versions chronologically.

Two utility functions are provided for direct comparison of protocol versions:
    `minecraft.utility.protocol_earlier` and
    `minecraft.utility.protocol_earlier_eq`.

Additionally, four methods are added to the `ConnectionContext` type to ease
the most common cases where the protocol of a given context must be compared to
a given version number:
    `minecraft.connection.ConnectionContext.protocol_earlier`,
    `minecraft.connection.ConnectionContext.protocol_earlier_eq`,
    `minecraft.connection.ConnectionContext.protocol_later` and
    `minecraft.connection.ConnectionContext.protocol_later_eq`.
2020-12-02 15:11:39 +01:00
..
encryption Add more encryption tests 2015-04-03 07:19:46 +05:00
__init__.py Made some tests for authentication. Still many tests to be made 2015-04-02 00:11:14 +02:00
fake_server.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_authentication.py Remove support for Python 2.7 2020-08-17 07:10:10 +02:00
test_backward_compatible.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_connection.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_encryption.py Fix issue #109 and add regression test. 2018-10-12 17:07:04 +01:00
test_exceptions.py Fix various problems in minecraft.authentication and its tests: 2017-03-31 12:59:43 +01:00
test_packets_with_logic.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_packets.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_reactors.py Fix: non-monotonic protocol versions are not correctly handled 2020-12-02 15:11:39 +01:00
test_serialization.py Fix: MultiBlockChangePacket.ChunkSectionPos reads/writes incorrectly 2020-09-10 16:35:53 +02:00
test_utility_types.py Fix: MutableRecord.__ne__ misspelt as '__neq__'. 2018-06-21 07:06:45 +01:00
test_version.py Add support for Minecraft pre-release 16w32a (protocol 301). 2016-08-11 10:40:50 +01:00