> ## Content Index
> Fetch the complete content index at: https://www.kenst.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# 2016 In Review
- URL: https://www.kenst.com/2016-in-review/
- Published: 2017-01-11T21:53:00.000Z
- Updated: 2023-02-06T21:17:17.000Z
- Author: Chris Kenst
- Tags: Year in Review, Writing

It’s a new year which means it’s time to look back at the previous year. Although this isn’t a lessons-learned or a progress report, these reviews are like a snapshot in time, forever preserved in writing. Unlike the past years I had no specific writing goals for 2016\. I knew my attention would be focused elsewhere and yet I still managed to write 13 posts, bringing this site’s total to [108](https://www.kenst.com/archives/)!

Popular posts don’t mean much but they are an interesting barometer of what others have found valuable.

You can find previous years here: [2015](https://www.kenst.com/2015-in-review/)

**Most popular posts of 2016, written in 2016:**

- [Trends in Testing Terminology](https://www.kenst.com/trends-in-testing-terminology/)
- [Selenium-WebDriver 2.53.x not working with Firefox 47+](https://www.kenst.com/selenium-webdriver-2-53-x-not-working-with-firefox-47-and-beyond/)
- [Review of The Selenium GuideBook: Ruby Edition](https://www.kenst.com/review-of-the-selenium-guidebook-ruby-edition/)
- [Debugging Selenium Code with IRB](https://www.kenst.com/debugging-selenium-code-with-irb/)
- [Running RSpec acceptance tests in TeamCit](https://www.kenst.com/running-rspec-acceptance-tests-in-teamcity/)y

The most interesting and/or valuable for me differed a little bit from this list. I enjoyed writing the [Selenium GuideBook review](https://www.kenst.com/review-of-the-selenium-guidebook-ruby-edition/) and was something I had wanted to do for a while. Writing the post on [Debugging Selenium Code](https://www.kenst.com/debugging-selenium-code-with-irb/) was great because I don’t use an IDE when developing Ruby scripts, I kept forgetting the steps, couldn’t quickly Google and so found it immensely valuable to write it down (and eventually share). [Selecting Platform Configuration Tests](https://www.kenst.com/selecting-platform-configuration-tests/) didn’t come out as great as I had envisioned it. However writing it forced me to deal with a combinatorial problem (device or configuration explosion) and then try to systematically make a choice about what I was going to test (sampling). It was fun and I keep thinking of other ways to apply it.

**The Future**

It’s 2017 so technically I mean the short-term future (including the present). I started a new job at a startup called Laurel & Wolf which means all kinds of fun changes and challenges (hopefully I will write about a few of them). I have yet to take the [State of Testing 2017](http://qablog.practitest.com/state-of-testing/?ref=kenst.com) but will be doing so shortly, so don’t you forget to sign up!

There are a number of testing topics I have been slowly tackling and unlike 2016 which seems to have been dominated mostly by tooling challenges, I plan to write about non-tooling topics. I haven’t yet sent out the first email to the amazing people on my email list but that will happen soon! 2017 is the year! If you haven’t already, join the [email list](https://www.kenst.com/2021/02/2020-in-review/#/portal/signup)!