• .NET Testing & ALM

    Stealing From The Company

    Greetings, fellow testers.  by  idleformat At a recent tech talk on automated testing and building, the statement was made that "not automating tests is like stealing from the company." The speaker’s intent was to stress the importance of what he believes to be a “best practice.” The focus of the talk was to encourage using unit tests and test-driven-development techniques; automating integration, functional and user interface tests; and including them at various points in the product’s build process. These are considered good, productive, time-saving techniques and so it should be obvious that not using them would be bad, ...
    June 14, 2013
  • .NET Testing & ALM

    The Power of Code

    Greetings, fellow testers. There's been a lot of talk recently about testers learning to code. I'll say this much here — I think it's important for those of us who are testing software to understand how software works. For some, that means being able to read code. For some, that will turn into an interest or passion for writing code. Some of that code will be automating existing tests, some of it will be automating other tasks that we perform every day — creating data, cleaning up after tests are complete, reporting on our findings, etc. With regard to automating ...
    June 12, 2013
  • Testing & ALM

    Hello World!

    Learn a little about new Developer Evangelist James Bender and how he'll be helping the community learn about the great Development Productive tools (JustMock, JustTrace, JustCode and JustDecompile) offered by Telerik
  • .NET Testing & ALM

    TeamPulse R1 2013 is Here with New Look, New Features

    Last year we embarked on a journey to take the product to a whole new level. Today we can show you the results - R1 2013 is now live! I’m definitely not exaggerating when I say this is our biggest release for the past 2 years.
  • .NET Testing & ALM

    Potential Project Killers – Part 2 – the Vague Budget

    In Part 1 of this five part series on potential project killers, I covered the concept of starting the project too fast. Starting the real work on the project before you’re ready can truly be a project killer. The project must be fully planned and prepared for – which I guess might make ‘the planning’ the real work on the project. In this Part 2, I’d like to discuss another potential project killer – the project with no real budget or at best a ‘vague’ budget. You might think, “No budget…nothing to manage against!” Well, that’s not exactly the ...