Skip to content
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

Finish testing suite #22

Open
elderamevans opened this issue Feb 11, 2015 · 4 comments
Open

Finish testing suite #22

elderamevans opened this issue Feb 11, 2015 · 4 comments

Comments

@elderamevans
Copy link
Collaborator

It's got a good start, but it definitely could use some more work.

Now the question is, what level would we want it to be? Make sure that login works, and basic functions work, or go after every single endpoint that the SDK has available, or somewhere in between?

Or something else? I have no idea how to make a testing suite......

@elderamevans elderamevans added this to the Publish to PyPI milestone Feb 11, 2015
@dangerwheeler
Copy link

My two cents... This will require effort, which means it can't be done all at once.

One approach would be to create a list of end-to-end scenarios that the SDK end users are likely to use and prioritize based on that (i.e. create tests for the most common scenarios first).

@elderamevans
Copy link
Collaborator Author

Eh, we don't need this to be published to PyPI, so removing that milestone.
Maybe in a future version...

@elderamevans elderamevans removed this from the Publish to PyPI milestone Feb 26, 2015
@elderamevans
Copy link
Collaborator Author

OK, good to know: We won't need a key for basic testing. I think the big thing is making sure hypermedia is working, and that logging in is possible. Although, how we can make sure that we can log in without actually logging in... I don't think FS would particularly like us deliberately sending bad requests, though.

Of course, we also need to have a way to tell when FS is down, and have a distinct "exit" message, saying that it was an external error, and to try again later.

@elderamevans
Copy link
Collaborator Author

I just realized:

We can have several different levels of test suites:

  • The "All Testable Functions Work" test suite
  • The "I can sign in just fine, and make a call to my person page" test suite
  • The ""Test every FamilySearch public endpoint possible, and clean up the sandbox afterwards" test suite.
  • etc.

I think the names are self-explanatory....

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

2 participants