SCRUM FOR our breakfast

-
I think this is a best intro to Scrum

Comments

Post a Comment

Popular posts from this blog

What is Exploratory testing

-
Image
As its name implies, exploratory testing is about exploring, finding out about the software, what it does, what it doesn’t do, what works and what doesn’t work. The tester is constantly making decisions about what to test next and where to spend the (limited) time. This is an approach that is most useful when there are no or poor specifications and when time is severely limited. Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used.
Read more

End-to-End Test

-
Image
Definition: End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish. The purpose of carrying out end-to-end tests is to identify system dependencies and to ensure that the right information is passed between various system components and systems. For example, a simplified end-to-end testing of an email application might involve: 1. Logging in to the application 2. Accessing the inbox 3. Opening and closing the mailbox 4. Composing, forwarding or replying to email 5. Checking the sent items 6. Logging out of the application
Read more

About front-end testing

-
I was asked many times about front-end testing: what to test and how to test it, and what tool are best to be used? And this is my final answer: You need to consider Mike Cohn’s analogy – the test pyramid. It will help you decide what kind of testing best to be done in a certain situation. At the bottom of the pyramid are the solid test units they are the foundation of the test strategy – they can provide you with a fast feedback. At the top, occupying the smallest part of the pyramid , are the UI tests. They interact with your UI directly(for example Selenium), but are costly and very slow on feedback. They can become very brittle and hard to maintain. At the middle of the pyramid there are integration tests that do not require an UI. In Rails, for instance, you would test your REST interface directly instead of interacting with the DOM elements. For smoke or regression tests UI are very useful. If there is a need to automate these, there are some dangers to consider. First, you shoul...
Read more