Skip to content

WIP: Initial tests for slskmessages#42

Open
droserasprout wants to merge 5 commits intopython3from
aux-slskmessages-tests
Open

WIP: Initial tests for slskmessages#42
droserasprout wants to merge 5 commits intopython3from
aux-slskmessages-tests

Conversation

@droserasprout
Copy link
Collaborator

First attempt to cover slskmessages module with unit tests and then clean up things a bit

@lene lene force-pushed the python3 branch 14 times, most recently from 657e1d0 to 9805bb6 Compare April 21, 2020 18:11
@toofar
Copy link

toofar commented Apr 24, 2020

Is the intent of these tests to show that the python3 migration hasn't broken anything or to allow for less guess work in refactoring? Because if it is the former they should be merged to upstream so they can be run against both versions and the latter I think it make sense to wait until after the python3 stuff is merged? To not make the PR even bigger and harder to review.
I'm not saying more tests are bad, just trying to temper enthusiasm for fixing everything at once in case the initial migration gets bogged down in feature creep. In particular I would like to add tests around the networking stuff to make refactoring it to be more efficient and handle more connections easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants