Our monthly meeting will be held at the Microsoft Greater PA Office in Malvern, PA on Wednesday, February 20 from 5:30-8:00. Refreshments are provided courtesy of philly.NET.
In this session we are going to look at the five things you need to know when starting to unit test your T-SQL code. After attending the session you will know how to pick a good unit testing framework, how to write your first test, how to spy on procedures, how to fake tables and how to deal with constraints. We will also briefly cover test case heuristics that help with these questions: “How do I pick the first test?” and “How many tests is enough?”
Today, the web isn’t what you remember.
It used to be stateless. Every call to your site began with a detective story of figuring out who the user was and hydrating their “state” so you
could continue useful work. The web didn’t remember state.
It used to be based on request and response. Code was delivered to the browser like a postman dropping off a package and speeding away. You had to call back in to get updates. Sure, we have AJAX to poll for updates these days, but those are just endless calls for new packages behind the scenes. The web wasn’t realtime.
It used to be filled with static applications. Users click on the buttons, controls, and widgets provided and the web application can only do
what the developer implemented. Sure, we “extend” web sites with REST “APIs”, but this isn’t the same thing as an SDK.
Start building extensible and powerful web applications after seeing how the way the web works is changing for good.