Productivity

The Data Access Visual Studio integration surely saved you time and effort while you were developing your data access layer. Now you need an easy-to-maintain configuration that will help you during the next stages of your application's lifecycle. Check out how to achieve it with the Data Access NuGet packages and code-only mapping.

Do your team's testers end up getting work late in the iteration/sprint/cycle/whatever? Are they tremendously backed up trying to get automation scripts written, validations done and exploratory sessions completed?

This blog post will provide you a summary of the R1 Test Studio release webinar, recording of the webinar and answers to a few interesting questions asked during the webinar.

This week, the Telerik® development team made the JustDecompile decompilation engine code open sourced under the Apache 2.0 license.

Many organizations are seeing tremendous benefits in moving to one of the various test-first methodologies such as Test Driven Development (TDD), Behavior Driven Development (BDD) or Acceptance Test Driven Development (ATDD). Test-first approaches improve team communication effectiveness, dramatically shorten feedback cycles and get testing activities working in parallel with development versus happening after development is complete. While we believe in the value of these methodologies, sometimes teams and organizations aren’t able to fully dive into them for a number of reasons. Regardless, teams can still see tremendous improvements even without wholesale adoption of “formalized” test-first methodologies. This blog post will help you formulate ideas to improve your testing activities and push them earlier, even without adopting a full-up methodology. All testing activities benefit from earlier collaboration with the team; however, functional user interface automation has some specific benefits that come out of early, effective collaboration.