Integration testing is a phase in software testing where individual software modules (or components) are combined and tested in a group. Integration testing happens after unit testing, and before system testing.
0
votes
1answer
41 views
Basic sign-up method, testable and with try/catch [closed]
I am learning how to implement testing and try/catch statements into my code. I have a Laravel application with the following ...
3
votes
1answer
80 views
Integration testing with in-memory databases strategy
I have an .mdf DB file and I want to use this DB for integration testing.
In every test I should:
Create a copy of an .mdf file.
Attach DB to an .mdf copy file
Do testing
Detach DB copy
Delete DB ...
6
votes
2answers
2k views
Generic wrapper for a task-based API
The idea was to provide a clear-looking, type-inferring framework to test a task-based API (it's for integration testing, and test methods should be as clear as possible).
All the tested API ...
2
votes
1answer
704 views
Integration test for database access
This integration test involves database access and hence opening and closing a database connection. Does it look correct? I am concerned about ensuring the the database connection is closed should the ...
1
vote
1answer
116 views
Rails integration testing: Should we use strings or named routes in http requests?
When integration testing Rails applications HTTP request helpers can take a string or a named route as the first argument.
I find myself writing:
...
