https://citconf.com/wiki/api.php?action=feedcontributions&feedformat=atom&user=EmilsitCitconWiki - User contributions [en]2026-04-24T21:37:56ZUser contributionsMediaWiki 1.35.11https://citconf.com/wiki/index.php?title=Test_Expressivity&diff=15358Test Expressivity2013-08-24T22:50:22Z<p>Emilsit: Raw notes</p>
<hr />
<div>Present: Emil, Jason, Andy, Rob, Monica<br />
<br />
* How should you organize your test suites? <br />
** During development? <br />
** Different from when they are considered regression tests? <br />
** Should they be weeded out<br />
<br />
* end to end tests<br />
** Should you even have them?<br />
** How many?<br />
** The test pyramid (http://martinfowler.com/bliki/TestPyramid.html)<br />
<br />
* Having requirements docs and test case docs <br />
** Very common, yet it's problematic; especially if they're at the same level of detail/abstraction<br />
<br />
* Challenges with dispersed teams <br />
<br />
* Clarifying tests with comments is not expressive? not expressive enough?<br />
<br />
* You should be able to show your business people your test code... <br />
** And they should be able to understand them<br />
<br />
<br />
----<br />
<br />
Howto build Maintainable test automation framework. How do you make it understandable. Reuse and abstraction. How much do you invest in these frameworks?<br />
<br />
Writing a book. Reasoning. Write what you want to read.<br />
How to sell it to other devs?<br />
<br />
How long lived is the business? How does test express what the business needs? Don't throw away tests that have taught you about the business.<br />
<br />
Don't align feature files with stories or work units. Write them along with the domain.<br />
<br />
Validate the tests? How do you have confidence that the test describes the behavior?<br />
<br />
Three amigos - business, tester, dev - all review stuff together.<br />
Imperative tests are hard for business people to think about.<br />
<br />
Review test code with business side<br />
Can you fold the code and get a good sense of it?<br />
<br />
Cucumber ... Do people like it?<br />
<br />
Do people understand the requirements?<br />
* be declarative<br />
* use the domain language<br />
* does the test explain why this test is interesting? Can you hide what is not interesting?<br />
<br />
Can you build reusable steps.<br />
Good logs and assertions to help find failures,</div>Emilsit