New answers tagged test-design
Test Driven Development (TDD) means that you write your tests before you write your code. So if you identified your class should be extracted from others there must be an individual reason to do so. So you should at least write tests for this individual functions. Depending on if you already have tests for the common functions of your class you (don't) need ...
For Android & iOS : You can refer this blog, it contains practical result to your queries
I've done it and basically I find these sorts of interviews come down to two main points. How well do you understand Test Plans, Strategies and documentation? Can you break down a project so that it communicates what you intend to do in a document that is handed to either someone outside your group or someone unfamiliar with your task. Can you communicate ...
You avoid this question completely by integrating testing into software development life-cycle. I assume you mean that the bulk of testing is done after development, rather than "how do we re-factor in the 11th hour of final testing"? General advice for re-factoring is to have good test coverage so changes can be made with confidence and have a high degree ...
Yes. Though to help make it easier on yourself, if you have a group of classes that have a set of behaviors that are the same, you can write tests that are applicable to the whole group...and then for each individual class you only need to write new tests for the unique behaviors (just copy the common ones). This method also helps keep consistency which ...
Every class with implementation has its own responsibility and behavior. So it is good to implement test that represent the class's behavior.
Top 50 recent answers are included