Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I know basic Specflow with .NET. I am looking for learning resources, ideally with code examples in .NET, other than below
http://www.specflow.org/, because the documentation is still lack of easy to read examples.
Here are some examples, some of them are a bit dated though:
Steven Sandersson http://blog.stevensanderson.com/2010/03/03/behavior-driven-development-bdd-with-specflow-and-aspnet-mvc/
TekPub intro http://www.youtube.com/watch?v=SVwBz-ZTliw
SpecFlow getting started http://www.specflow.org/getting-started/
Writing maintainable test code: http://www.marcusoft.net/2011/04/clean-up-your-stepsuse-page-objects-in.html
I think the documentation is pretty good for when you got up and running.
A very good course by Jason Roberts at Pluralsight.
"Business Readable Automated Tests with SpecFlow 2.0", covers topics like following:
High Level SpecFlow Overview
SpecFlow Technical Features Overview
Understanding the Feature File Format
Step Definition Code
Getting Started in Visual Studio
Step Definition Binding Styles
Creating the First Scenario
Running and Debugging Test Scenarios
Four Ways to Improve Maintainability
Introducing Parameterized Step Definitions
Introducing Scenario Outlines
Creating Common Setup Code with Scenario Backgrounds
Dynamic Step Table Data
Passing Data Between Step Definitions
Using Context Injection
Restricting Step Execution with Scoped Bindings
Executing Code Before and After Every Scenario
and more...
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 days ago.
Improve this question
We are following the agile process of Scrum and using Jira. What issue type and workflow do teams use for exploration tasks? These would be tasks to learn the different options to achieve a story. For example, we need to move data from one DB to another, first explore options based on our current tech stack and new options available in the market. We are considering creating a new Jira type instead of using Story.
This is called a "spike" in agile terminology. You create and track the work to be done on the unclear parts of a story under a spike.
For the detailed information, you can read this article at wrike.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
From what I can tell from online forums and posts, one of the main focuses of BDD/ATDD seems to be on discussion and ensuring that the customer, developers, testers and other relevant parties are involved in the understanding what the system must do.
Question 1: Do BDD/ATDD stories replace the need for traditional requirement specifications, such as the those captured using the Volere Template?
Because the traditional requirement specifications are one of the key inputs for developers and testers, traditional requirement specifications tend to be comprehensive.
Question 2: Should BDD/ATDD stories also be comprehensive enough to allow a system to be fully tested?
Question 1: Instead of looking at this question as a black-and-white situation, we should better understand how these two requirements capture methods get along with each other. Writing a story in the BDD/ATDD methodologies, or in Scrum for example, does not imply removing the templates like volere off the table. If we take a look at the volere requirements specification here, we can see that most of the information regards to project-related issues, and the shell used for functional requirements is far from being different to a story. They just have different information, not exclusive one.
Question 2: Here we have the advantage coming from the methodology itself. BDD comes from TDD, we can more or less rely on the test-first oriented process to allow the team to test the system. But, as I mentioned in question 1, making a BDD/ATDD story more comprehensive is not a sin, and wouldn't compromise the general idea of the story. This would also prove useful when interacting with more experienced clients.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm still relatively new to iOS development and also an absolute stranger to any kind of testing that is not compile, run, and check whatever comes to your mind.
This is obviously a weakness on any developer's profile and I'm decided to get ride of it now that interesting, real projects are coming my way.
In my quest to look for the best approach to go from 0 to 100 as soon (and well) as possible I'm coming to the specialized community to get your feedback.
At the same time I'm asking for your tips I'm also getting into Amazon to look for well-reviewed books on the subject and Google to get the rest. I'm just coming here to gather the feedback of those willing to spare a minute or to so I can probably hit jackpot with a great advise and better plan my learning strategy.
Thats right. For my job testing and test driven development is indispensable.
I often use Java and JUnit, but for Objective-C and XCode I think this screencast is a very good start: http://qualitycoding.org/objective-c-tdd/
Since I watch this screencast I use OCHamcrest and OCMockito (both explaind in this screencast) as well as SenTestingKitAsync for testing asynchronous functions.
I think the Clean Code book is a must have for every developer. There is a chapter about testing.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I'm a seasoned Symfony 1.4 developer with a good handle on Symfony 2.0, so I'm a bit beyond the basics of frameworks.
I've recently built a solution with Rails 3 and would like to pick up a book to read up on how I could have done some things better.
I'm mostly using Rails as a database layer with very minimal in the ways of ERb. Some topics I'd hope to see covered in advanced detail are:
JSON
Ideas and opinions on how to serve rich internet applications
Good ActiveRecord usage and planning
Writing models and keeping implementation out of controllers
In general, conventions on controllers and actions
There are likely many subjects I'd like to hear about however I'm not interested in focusing too strongly on testing quite yet.
Haven't read this book, but it seems really good Ruby Science
After spending a bit of time with some of the books from the comments above, it looks like Rails Antipatterns is still quite worthwhile.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I'd like to start using continuous integration in my personal projects to get experience with the techniques and concepts. The problem is that my programming poison runs to the non-mainstream (to put it mildly) with the bulk of my work being in Erlang.
What continuous integration systems are capable of dealing with non-mainstream languages, chief among them, in my case, Erlang? How easy are they to set up, configure and run?
At this point I'd recommend Jenkins. It is easy to setup and configure, there are lots of help online and basic support with the common Erlang test tools.
See Stack Overflow question Continuous integration server for Erlang code for basic information about how to intergrate eunit and common test into Jenkins.
We are using Jenkins-CI in the etorrent project and that seem to work really well. We have a number of virtual machines implementing different operating systems on which we run the system and then carry out tests.