Skip to content

unittest.TestCase Suites are needed for all Interfaces/Methods #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
michaeljohnbarr opened this issue Jul 24, 2013 · 0 comments
Open
Assignees

Comments

@michaeljohnbarr
Copy link
Owner

With the utilization of Python's unittest, we will be able to better handle any regressions which happen for any commits. This also includes the fact that the Steam Web API may change at any given point.

@ghost ghost assigned michaeljohnbarr Jul 24, 2013
michaeljohnbarr pushed a commit that referenced this issue Aug 1, 2013
…'s base directory to ignore *.pyc files. Created a test for the core.py: SteamWebAPI class per Issue #4.
michaeljohnbarr pushed a commit that referenced this issue Aug 2, 2013
…y by removing DEFAULT_FORMAT, which will not be used.
michaeljohnbarr pushed a commit that referenced this issue Aug 4, 2013
#3). Fixed a bug in URL formatting where the logic allowed appending the '&format=<name>' multiple times. Updated test_core.py to test the content-type returned in the header of the request. This will make sure that we are getting the correct response type for XML, JSON, and VDF requests (Issue #4).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant