Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you should not change your test code.</p> <p>Why? In TDD, you define a interface for a class. This interface contains methods that are defined with a certain set of functionality.The <strong>requirements</strong> / <strong>design</strong>.</p> <p><strong>First:</strong> These requirements do not change while refactoring your production code. Refactoring means: changing/cleaning the code without changing the functionality.<br> <strong>Second:</strong> The test checks a certain set of functionality, this set stays the same.</p> <p><strong>Conclusion:</strong> Refactoring test and refactoring your production code are two different things.</p> <p>Tip:When write your tests, write clean code. Make small tests. Which really test one piece of the functionality.</p> <p>But "Your design changes because of unforeseen changes to the requirements". This <strong>may</strong> lead or <strong>may not</strong> lead to changes in the interface.<br> When your requirements change, your tests must change. This is not avoidable.<br> You have to keep in mind that this is a <strong>new</strong> TDD cycle. First test the new functionality and remove the old functionality tests. Then implement the new design.</p> <p>To make this work properly, you need clean and small tests. Example:</p> <pre><code>MethodOne does: changeA and changeB Don't put this in 1 unit test, but make a test class with 2 unit tests. Both execute MethodOne, but they check for other results (changeA, changeB). When the specification of changeA changes, you only need to rewrite 1 unit method. When MethodOne gets a new specification changeC: Add a unit test. </code></pre> <p>With the above example your tests will be more agile and easier to change.</p> <p>Summary: </p> <ul> <li>Dont refactor your tests, when refactoring your production code.</li> <li>Write clean and agile tests.</li> </ul> <p>Hopes this helps. Good luck with it.</p> <p>@disclaimer: I do not want your money if this makes you rich.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I ensure that I don't break the test code when I refactor it?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMats Stijlaart
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGreat but this misses the point IMO. The question was not about changing the test code as a result of changing the requirements. It was about *refactoring* the test code. "Dont refactor your tests, when refactoring your production code." => this principle is implicit in TDD. You you always re-run the tests between 2 refactoring actions, taking one baby step at a time.
      singulars
      1. PO
      1. USguillaume31
    2. COI understand your statement. I refer to the fact that you have to write clean test, this way you don't need to refactor the tests. When you think this is not possible, you should follow the principle for testing your methods specification by specification. This way you can create tests that are as small and relevant as possible. Ok and sometimes you have to refactor your tests. There is only one explanation: You are never sure about refactoring unless you have tested the implementation. This translated to the question: you can only achieve this by testing your tests (which is overkill).
      singulars
      1. PO
      1. USMats Stijlaart
    3. CO@MatsStijlaart I've coached a couple of teams who just started out with unit testing. They don't write there test clean from the start. I've taught them how to use patterns like Builder to clean up there tests,to split tests to test only one thing and other things to make sure that the team doesn't stop writing tests because it's to hard to use them.
      singulars
      1. PO
      1. USWouter de Kort
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload