08. Getting Testing Done in the Sprint – Write Logical Acceptance Tests

During release planning meeting. Capture acceptance criteria and immediately add the as logical test cases to the PBI. It will help the team to understand, clarify the discussion and more important for this topic, it helps testers be involved, and be important at the early stages of the software cycle. Within VS11 | TFS11 this is very easy to accomplish: add the PBI to the backlog. add logical test cases, from the backlog item work item. and only add the test case title. Start planning and execute the sprint open Microsoft Test Manager, add a test plan for the current sprint. Add the Backlog items as Requirement Suites to the plan and see th... [More]

07. Getting Testing Done in the Sprint – Risk and Business driven Tests

I really like the mindset “no risk, no test”. So, when there isn’t any business risk, there aren't any tests and is it easy to fit testing in a sprint. More realistic do a good risk analysis on your product backlog items before start writing thousands of tests. Also in scrum is risk an important attribute. The release plan establishes the goal of the release, the highest priority Product Backlog, the major risks, and the overall features and functionality that the release will contain. Products are built iteratively using Scrum, wherein each Sprint creates an increment of the product, starting with the most valuable and riskiest. Product Backlog items have the attributes of a desc... [More]

Create a TFS11 on Azure account with Clemens and get a 3 minute quick start explanation … #techdaysnl

TechDays in Den Haag, Netherlands TFS11 Service is the brand new Team Foundation Service on Azure, it makes it very simple to have your own Team Foundation Server. But, there are some new concepts in TFS11. In a 3 minute face to face session with me, we create a TFS11 on Azure account and you get an explanation of these new concepts so you can start using it and be productive immediately. Look for this laptop at the Sogeti boot or ATE area at the TechDays in Den Haag, Netherlands. Thursday only. Tweet !function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBe... [More]

Decks: TFService Basic and Advanced

Decks I used Yesterday for a TFService presentation. Normally it is a demo only presentation, but a scheduled maintenance made me use them (see http://blogs.msdn.com/b/tfservice/ for the schedule).  Lucky me I have them, now you have hem too… First presentation (second in the series, first session was about scrum 101) is some general usages of TFService and how it supports an agile way of working. TFS11 on Azure the basics View more presentations from Clemens Reijnen.   Second deck (fourth in the sessions series, third one was about how we use it in real projects) is about how we solved some usages challenges like multiple backlogs, bug backlog, testing etc.  TFS11... [More]

06. Getting Testing Done in the Sprint – PBI Implementation Sequence

A challenge in getting testing done in a sprint is the fact that the software (PBI) isn’t ready to be tested till implementation/ coding is done.  How To. Work on completing each item in the sprint backlog and finish one item after another, see task boards below. BAD -- Not able to start testing task board, every team member works on a different pbi. Testing can only start at the end of the sprint. GOOD -- Ready to start testing task board, team members work together on a pbi one after another till it’s done. Testing can start early. It is a good practice, but not often followed. it really helps getting testing done.   Past Tips: 01. Getting Testing Done in t... [More]

05. Getting Testing Done in the Sprint – No Double, Triple Testing

One way of getting testing done in a sprint is making it [testing] as efficient as possible, meanwhile this also saves money. One way of getting more efficient is not doing things double or triple. An interesting thing with testing, we do test double or triple. We test it during unit, during unit integration, during functional and during acceptance testing, this can be done better, we could save a lot of time. I’ve seen teams which also automated all these types of tests, testing the same thing... not really efficient, they didn’t manage to get it done in a sprint. Each phase of the development process has its own test goals and depth of test coverage. The depth particularly depends upon th... [More]

04. Getting Testing Done in the Sprint – Undone Backlog Item

A tip straight from the previous Scrum Guide (The guide updated and the undone TIP is removed, read The 2011 Scrum Guide – A Lot of Changes! ). But, the TIP still works, although it isn’t an ‘official’ tip anymore… Undone End to End Testing End to end testing, is not an agile specific testing practice, it’s a common sense testing practice. Create test cases to detected defects anywhere in the chain. This type of testing has been growing the couple of years enormous due to the rise of Service Oriented Architectures and more recent Cloud Computing.  as the TMap end-To-End Testing books describes “End-to-end testing is a form of testing in which the (business) process is tracked thr... [More]

03. Getting Testing Done in the Sprint – Test Automation

Automate your testing effort, or better your test execution, is a must to get your testing done during the sprint. Automate your test execution shrinks the time needed to execute the tests, which leaves more time for the team to specify new test cases. On the other hand it also brings some inflexibility in your testing, you need to maintain the test automation code and update it when functionality change, which again cost time which the team better could use to specify and execute test cases. How to. So, there need some strategy what to automation and how to automate. The decision what test cases are candidate for automation depend on several decisions. For sure the regression set is a go... [More]

02. Getting Testing Done in the Sprint – Regression Test Sets

Some teams rerun every test every sprint, this is time consuming and isn’t worth the effort. Having a clear understanding what tests to execute during regression testing raises the return of investment of this testing effort and gives more time to specify and execute test cases for the functionality implemented during the current sprint. How To. So, collecting a good regression set is important. There area lot of approaches how to get this regressions set, most of them are based on risk classifications and business value (see TIP 07. Getting Testing Done in the Sprint – Risk and Business driven Tests). From “A good regression test is invaluable.” The principle is that from each test ... [More]

01. Getting Testing Done in the Sprint - The Team and Activities

Every Agile ALM presentation the same question is asked: How do I get testing done in a sprint? There isn’t a one solution/ practices/ to do/ how to fits all for this. So, I made a small list of tips you could do (or recommended to do, or must do… ), which can help to get testing done in a sprint.  Tip 1: Have testing knowledge in the team. Actually not a tip, it is a must. This is a kind of obvious but not common and I think the hardest thing to accomplish. It is: get testing knowledge available in your team. When you don't have it, you will fail. How to Now, it isn’t that easy to accomplish this collaboration. Test and dev are different, a nice quote from this ‘test’blog: ... [More]

Şarkı Sozleri