This article is in a series about Selenium and SpecFlow Introduction Why bother? Basic plumbing Page objects The engineering behind decent Gherkin files This series contains an article about how to store and use information when executing a test in a way that lets you write nice Gherkin. That is a bit more of an … Continue reading SpecFlow + Selenium: Basic plumbing
Category: Testing
Why bother testing your website with Selenium and SpecFlow?
This article is in a series about Selenium and SpecFlow Introduction Why bother? Basic plumbing Page objects The engineering behind decent Gherkin files This is not a general Why bother with testing? post, but instead gives some specific business benefits of testing your site with something like the combination of Selenium and SpecFlow. You will … Continue reading Why bother testing your website with Selenium and SpecFlow?
Introduction to testing your website with Selenium and SpecFlow
This article is in a short series about testing your website with Selenium and SpecFlow: Introduction Why bother? Basic plumbing Page objects The engineering behind decent Gherkin files The combination of Selenium and SpecFlow lets you do two useful things: Test your website in the way that a user would Base these tests on acceptance … Continue reading Introduction to testing your website with Selenium and SpecFlow
Finding your testing path
Introduction There is usually a lot of testing that you could do next, but which should you do next? Which test is the most valuable? This article suggests a way of navigating through your set of tests, which has implications for which tests you should write when, when you should run them and for what … Continue reading Finding your testing path
Dealing with transactions in tSQLt
This is the last article in a series about unit testing SQL Server with tSQLt: Introduction Anatomy of a tSQLt test Practical considerations Dealing with transactions The problem In my experience, most code is fine to be tested with tSQLt. However, code that involves transactions will get tangled up in the transaction that tSQLt uses … Continue reading Dealing with transactions in tSQLt
Practical considerations with tSQLt tests
This is the third article in a series on tSQLt: Introduction Anatomy of a test Practical considerations Dealing with transactions Getting organised One stored procedure under test is likely to need several stored procedures to test it properly. This means that the number of stored procedures in your database will increase greatly. (This is one … Continue reading Practical considerations with tSQLt tests
Anatomy of a tSQLt test
This is the second in a series of articles on tSQLt: Introduction Anatomy of a test Practical considerations Dealing with transactions Splitting into files and running tests tSQLt organises test cases into test suites. A test case is a stored procedure whose name starts with the word test. A test suite is a schema that … Continue reading Anatomy of a tSQLt test
Introduction to unit testing SQL Server stored procedures with tSQLt
This article is the first in a short series on tSQLt: Introduction Anatomy of a tSQLt test Practical considerations Dealing with transactions Introduction This is the introduction to the introduction! tSQLt lets you unit test stored procedures (including functions) on SQL Server. For why unit testing is a good idea, see my article on unit … Continue reading Introduction to unit testing SQL Server stored procedures with tSQLt
Why bother testing?
There have been quite a few posts here about testing, and I expect that there will be several more, but so far I haven't addressed a fundamental question: Why bother testing? It's something that's good for the soul but you don't (usually) get paid for shipping tests, just for the production code and documentation. To … Continue reading Why bother testing?
Testing a Web API
If you write a Web API (I’m using this to mean any API that you call via HTTP, such as a REST API using the Microsoft Web API framework), the world it’s part of is: It’s likely that while you’re developing, Client machine = Web server machine = Database machine, but this might not be … Continue reading Testing a Web API
Random Tech Thoughts 