acceptance-testing

I'm loving the BDD approach to development, but I've bumped into a concern with how far to go. This comment from ThoughtWorks most recent Radar gives me pause: "The advent of behavior-driven design (BDD) testing frameworks like Cucumber, combined with browser automation tools like Selenium, has encouraged widespread use of acceptance testing at the browser level. This unfortunately encouraged doing the bulk of testing where the cost to run the tests is the greatest. Instead, we should test at the appropriate level, as close to the code as possible, so that tests can be run with maximum

I am using nightwatch and trying to iterate through a list of elements. However, when I don't get objects or elements, but I get an array of strings. CODE browser.elements("css selector", ele, function(r){ browser.perform(function(){ console.log("LIST", r); }) }) RETURN LIST { sessionId: 'b273b874-c084-4d17-8bbe-a911a170ef25', status: 0, state: 'success', value: [ { ELEMENT: '6' }, { ELEMENT: '7' }, { ELEMENT: '8' }, { ELEMENT: '9' }, { ELEMENT: '10' }, { ELEMENT: '11' } ], class: 'org.openqa.selenium.remote.Response', hCode: 995684858 } The value should be returning an object of webElements

Here is a test description, testing the "Create New Widget" use-case. Confirm that you can enter a new widget into the system. Here is another test description, testing the "Create New Widget" use-case. Bring up the application. Create a new widget by the name of "A-008", with the description being "Test Widget for Acceptance Test 3-45". Confirm that the widget is now visible in the leftmost widget tree view. Select another widget in the tree view, then select the widget "A-008" again. Confirm that the values in the widget display equal the values you entered. Delete widget "A-008" and close

With the release of Rails 5.1, they included system tests. Which means we can test our JavaScript too in Rails. I see Rails guide explains a sample test creating article in both ways: via system test and via integration test. Now the question is: before Rails 5.1 I was writing complex test cases in integration tests. But now I have two options to write a test case. I can write test case like test: should create article in integration test, but I can also write the same test case in system test. So when should I choose system test to write a test case and when to choose integration tests ? The

I think I thoroughly understand the concepts and ideas behind SpecFlow, but even after reading the Secret Ninja Cucumber Scrolls , The Cucumber Book , and going through the various forums I'm still unsure about the path to reusability. Our scenarios already comply to various guidelines Self explanatory Must have a understandable purpose (what makes it different from the other scenarios) Are unique Represent vertical functional slices Uses Ubiquitous Language Written from the stakeholder perspective About business functionality, not about software design Grouped by Epics ARE NOT TEST SCRIPTS

Are you for one or the other? Or both? My understanding is unit tests: validate the system from the developer's point of view help developers practice TDD keep code modular assist in detecting errors at low levels of granularity Acceptance tests: validate the system from the business and QC / QA points of view tend to be high level as they're often written by people not familiar with the inner workings of the code I feel both are necessary. However, for minimization of redundant work, is it a good idea to try to incorporate unit tests into acceptance tests? In other words, have the latter call