- Removed PHP 7 support. The tests which checked whether the ajax
  features are working, those were failing in case of Drupal 8.5 and PHP
  7.
- Drupal 8.5 support has been removed earlier. You can see it
  [here](https://github.com/subhojit777/dc_ajax_add_cart/commit/c24e55bf74dfc0b7b335fafb555993323d7ecfb9)

- Added more tests:
  - Test whether the update cart button is indeed ajaxified.
  - Test whether the order total is correct after quantity update.

- Fixed random failing test. The fix is done by removing the randomness
  in the test.
- I was unable to find the reason why quantity didn't get updated in case of the
  first product variation. The test failed asserting that for the first
  product variation the quantity is updated. The test was passing when
  second product variation was randomly chosen to be updated. Even in the test
  screenshots it clearly showed that the quantity is updated for the
  first product variation.

- README updated.

- This is done to suppress deprecation warnings.

- Changes made in the other test view, so that the test helper functions
  can be reused, without changing CSS class.

- Maybe I forgot to change the xpath query that I used for testing. Maybe I was
  drunk or something.

Issue #2935858 by subhojit777: [Test Improvement] Move common setup tasks to the views base test class

- Fixed failing test.
- For PHP 5.6 the tests were failing because it can't access the cart
  without `access cart` permission.

- This fixes the stalling tests on TravisCI.
- Earlier I thought that the problem is in the tests itself, but later
  confirmed that the problem is with PhantomJS.
- The issue was due to PhantomJS. PhantomJS 2.1.1 + Ubuntu Trusty is the
  reason the tests were stalling. But recently, after Googling and debugging I
  was quite sure that the stalling problem is due to PhantomJS 2.1.1.
  There I have also restricted PhantomJS version to 2.0.0.
- I was able to replicate this in my local also. Tests in local never
  worked if PhantomJS and the tests are run in the same window.
- How the tests worked earlier is still unknown. And for the sake of
  progress, I have decided not to spend more time on investigating this.
  I have already spent a month trying to get it work.
- Thanks to [Pasi Kauraniemi](https://github.com/mitrpaka) for
  confirming the problem.
  https://github.com/drupalcommerce/commerce/pull/765#issuecomment-355888268

- Borrowed the idea from drupalcommerce/commerce. Thanks to Matt Glaman.

Issue #2930680 by subhojit777: [Test Improvement] Check whether the product is gone from the backend also

- Fixed an incorrect logic.

Issue #2930680 by subhojit777: [Test Improvement] Check whether the product is gone from the backend also

- Test improvement:
  - Test added that if remove button views field is not ajaxified, then
  the product row stays in the UI.

- Additional tests:
  - Test checking whether the remove button views field is indeed
  ajaxified.

- Implemented the actual feature.

- Tests updated:
  - Now the test is going to check (visually) whether the product is indeed
  removed from cart, and the other product is still there.

- Tests updated:
  - The view test has been updated so that it can uniquely identify
    variations per row.
  - Some test methods have been added to support the changed view.

- Code improvements:
  - A common assert function is created which would check the ajaxified
  cart page.

- Init tests.

- The ajaxified remove button.