After a few embarassing announcements, and failed launches, I have successfully re-crafted my websitefor 2100 Solutions Consulting, LLC. This branding of my services includes, Program Management, BPM Strategy, Quality Assurance, Testing, Performance Preparation and Strategy, Automated Testing and Product Development.
Here is a URL for the Ruby on Rails website I just launched using the Heroku enviornment this weekend. http://2100solutions.com
Heroku was by far the easiest host to implement.
Now a stable 24/7 presence with links to my external blogs and pursuits.
I have other RoR websites completed, but not yet launched on Heroku. All published websites will be managed through GitHub. My account at GitHub is WAFulbright, if you’d like to see or follow or contribute to my code! Let’s do talk before you contribute! Thanks!
Wow! That is a mouthful, but well worth reading in this great and stirring article on Context Driven Testing by Cem Kaner http://context-driven-testing.com/?p=69
This is an outstanding article on the DISTINCTIONS and False Dichotomies that need to be clarified and observed when planning and writing test cases: manual vs automated, checking vs testing …. or ‘sapient’ (is this a new test term or is it an attempt to marketize a concept?)
“…According to the ?new doctrine?, only manual testing can be sapient. Automated tests are done by machines and machines are not sapient. Therefore, automated testing cannot be sapient. Therefore, if a tester is enthusiastic about sapient testing (whatever that is), automated testing probably won’t be of much interest to them.”
It also Invites ond, as Ron Jeffries puts it in the comments: “…to look at the question from different angles, and the message that I get is that there is no bright line anywhere to be seen. That matches my deepest intuitions and gives me a kind of comfort.”