Functional Testing
Learn how to use Fume to test your changes.
Best code reviewers actually checkout to the head branch and run the application to make sure that the changes they are reviewing actually work as intended. Engineers are usually biased towards their own code and only test poorly. Fume can automate this process for you.
Fume will run your application and test it against a set of tests. If the tests pass, Fume will comment on the pull request with a success message. If the tests fail, Fume will comment on the pull request with the failure message and a link to the test log.
These test are usually in one of the following formats (but Fume sometimes find more creative ways too):
- Browser testing (if your application is a web app)
- API testing (if your application is an API)
- Writing new automated tests (if your application already has tests)
- Writing ad-hoc test scripts
What enables Fume to do this is the isolated development envrionment that it has access to: Studios. However, you should set up the project in Fume's studio first - just like you would do for a new-hire onboarding. Here is more about how to set up your project in Fume's studio: Studio Setup.