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

Integration Tests #19

Closed
bbatsche opened this issue May 24, 2015 · 1 comment
Closed

Integration Tests #19

bbatsche opened this issue May 24, 2015 · 1 comment

Comments

@bbatsche
Copy link
Owner

bbatsche commented May 24, 2015

Mock class and unit tests allow us to make sure we are hitting the API endpoints we think we should, but are those the right endpoints really? Do they do what we think they do? What if we made the same typos in both Verify and in the unit tests? And what if they change?

Create a suite of full integration tests, similar to the former "unit" tests. Don't need to go too deep; we don't need to test PHPUnit's functionality, just test that when we run:

verify(true)->isTrue()

the test really does pass.

@bbatsche bbatsche added this to the 1.1.0 milestone May 24, 2015
@bbatsche bbatsche removed this from the 1.1.0 milestone Jun 1, 2016
@bbatsche bbatsche added this to Backlog in BeBat\Verify May 13, 2019
@bbatsche
Copy link
Owner Author

bbatsche commented May 5, 2022

Used this approach when writing tests for Verify 3.0.

@bbatsche bbatsche closed this as completed May 5, 2022
BeBat\Verify automation moved this from Backlog to Done May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
BeBat\Verify
  
Done
Status: Done
Development

No branches or pull requests

1 participant