Integrate Countersign Test with airSlate SignNow

Integrate countersign test

Another major force multiplier in reducing my coding time for Oxbridge Notes (https://www.oxbridgenotes.co.uk/) down to a few hours a month, was creating thorough integration tests. To start off slow, let me run a sample test. I'm running this in NO_HEADLESS mode, so you can actually see the browser execute the tests. It went very quickly, and you saw how the browser fills in all the form fields and navigated from page to page. It’s essentially simulating a real user. Normally, you would run such a test in HEADLESS mode, so that it doesn't get in the way of your ability to code, and distract you. Furthermore, you'd probably be running it on a continuous integration server, which I'll cover later in this episode. You can see on the screen that a bunch of tests passed. For example, Creating A Seller does not create an invalid user when an empty form is submitted. And a Normal seller with cookie notice tracking can apply to itself, etc. etc. If it seems to you like more tests have passed here than we actually saw in the browser, then that's correct. That's because the HEADLESS variable is only for my JS tests, not for my HTML-only tests. I'll go more into that distinction later in the episode. Let's go over to the code and see what all of this corresponds to. I'm going to open up a particular spec; this create_seller_ spec. Yeah, there we go. Now, inside this file, the first thing you'll see is this before block. This gets executed before every single test in this file and all it does is use some factories to create some necessary database context. For example, a certain commission_amount should exist in order to display that page, what commission each seller gets and there should be some discipline_names. Disciplines that I’m selling, in order to populate the form where the seller chooses what discipline they'd like to sell on the website. There's also this email which the prospective seller is going to type into that form. I share this throughout all the examples here. Now let's get down to the test itself. It’s js: true, this essentially means that we’re going to use a JavaScript driver as opposed to a purely HTML driver. What actually happens in the test? We visit some particular URL, the new_seller_url. This is a named URL which turns into the actual URL. We accept some advanced tracking, this is defined over here. It just means "click on I accept in the JavaScript thing 02;25". Then we fill_in_seller_form_fields. This is also a custom piece of code because I share this throughout multiple tests, and it gets modified here with some extra fields. I fill in seller_description with the text SMART Study. I attach a file to the seller_doc id, and that file is found in Rails.root plus some particular fixtures - the robots.txt. I use that particular file because it’s extremely small and the test will run more quickly. I select...