1 / 22

FitNesse in Fifty Minutes

FitNesse in Fifty Minutes. Chris Harbert Resonate. What is FitNesse ?. FitNesse is an open source collaboration and testing framework based on the wiki concept .

magar
Download Presentation

FitNesse in Fifty Minutes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FitNessein Fifty Minutes Chris Harbert Resonate

  2. What is FitNesse? FitNesse is an open source collaboration and testing framework based on the wiki concept. Written by Robert Martin (a.k.a “Uncle Bob”), a software consultant and prolific author who was one of the original signers of the “Agile Manifesto”.

  3. What is FitNesse? Wiki pages are suites, tests, or static pages. Suites are organized into hierarchies. • TestSuites • TestSuites.SuiteOne • TestSuites.SuiteOne.TestOne • TestSuites.SuiteOne.TestTwo You can run at the suite level or at the test level. http://yourfitnesseurl/TestSuites.SuiteOne?suite http://yourfitnesseurl/TestSuites.SuiteOne.TestOne?test

  4. When to use FitNesse? Collaboration You want to encourage more collaboration around requirements and testing.* * Results not typical.

  5. When to use FitNesse? Documentation You want your tests to serve as documentation. The good kind.

  6. When to use FitNesse? Share the love You want to provide the ability to write automated tests to a technical, but non-developer audience.

  7. Example #1: Web Test (BDD)

  8. Example #1: Web Test (BDD)

  9. Example #2: Database/ETL

  10. Example #3: Compare Excel Files

  11. Example #4: Compare Query to Excel

  12. Example #5: Verify Excel File Contents

  13. Example #6: Taking Screenshots

  14. Example #7: HBase

  15. Other Fixtures • CSV File • REST API • Command Line / SSH • JIRA (e.g. to assert the ticket status) • PDF • Check Email

  16. Creating Your First Fixture Steps • Identify a test (or create one) that needs a fixture implemented. • Select the appropriate fixture type.* • Implement the methods that fixture type expects. • Run the test. * Fixtures can actually implement multiple fixture types simultaneously. In some cases, existing classes can be used as is.

  17. The Basic Fixture Types Source: FitNesse User Guide

  18. Options for Running Tests • From the UI • From the Command Line • Using the web URLs • … with HTML response • … with XML response  useful for integration w/ build servers, TCM systems, etc.

  19. Additional Cool Stuff and Tips • Suite filters allow you to run any tests with a given tag. • Symbols can be used to pass data around. • Use SLIM tables, not older fixtures. • Use collapsed sections to hide setup and teardown in order to increase readability.

  20. When NOT to use FitNesse? • You’re writing fine-grained unit tests. • Only developers will see them. • No one can write fixtures.

  21. Caveats • Requires developers to provide appropriate fixtures (which may be re-usable by non-developers). • No parallel runs (out of the box ;) ). • Is FitNesse dead?

  22. Resources • The website, http://fitnesse.org/ • The User Guide (included in link of install) • The repo, https://github.com/unclebob/fitnesse

More Related