Don't throw exception is there was no response. It might just be that we didn't send the request because the checkbox wasn't checked.
Allowing the batch to run without having to check the "Using SmartyStreets" checkbox first.
Telling users to open a nonprofit SmartyStreets account.
Making properties static and setting them in the constructor.
Sending requests both for zip codes and addresses in the batch addr verification process.
Updating address verification mocks.
Refactoring the validator tests.
More refactoring. Updates no needed anymore.
Working on the batch address verification. The test fails right now.
The single and multiple batch address verification tests pass now.
Testing batch address and zip code together.
Fixing ADDR Verification Gateway test.
Putting the API_Response__c field back in the batch query. The test was not catching the error because the exception was being caught.
Checking Using SmartyStreets checkbox when running batch.
Merge dev into feature/850-addr-verif-batch-test
Merge pull request #869 from SalesforceFoundation/feature/860-too-many-batch-jobs

Feature/860 too many batch jobs
Merge dev into feature/850-addr-verif-batch-test
Merge pull request #872 from SalesforceFoundation/feature/860-too-many-batch-jobs

Feature/860 too many batch jobs
Merge pull request #874 from SalesforceFoundation/feature/860-too-many-batch-jobs

Feature/860 too many batch jobs
Merge pull request #875 from SalesforceFoundation/feature/860-too-many-batch-jobs

Fix namespacing in Global Layout