This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Secure TDD Project"
Lauren Tabak (talk | contribs) m |
Lauren Tabak (talk | contribs) m |
||
Line 29: | Line 29: | ||
'''Difference between TDD and Unit Tests''' | '''Difference between TDD and Unit Tests''' | ||
− | |||
+ | So how does a TDD test differ from a unit test? Unlike a unit test, a TDD test is used to drive the design of an application. A TDD test is used to express what application code should do before the application code is actually written.<br> | ||
− | How do we solve the problem by implementing STDD? | + | TDD is less about testing, and more about designing the code. Unit tests are then used to set the expectations for the end code.<br> When the end code is written, and passes tests (specifications), you have code that was designed using tests.<br> |
+ | |||
+ | |||
+ | Like unit tests, TDD tests can be used for regression testing. You can use TDD tests to immediately determine whether a change in code has broken existing application functionality. However, unlike a unit test, a TDD test does not necessarily test one unit of code in isolation. <br> | ||
+ | |||
+ | Like acceptance tests, TDD tests are used to drive the creation of an application. TDD tests work like mini-acceptance tests. You create a TDD test to express the application functionality that needs to be implemented next. However, unlike an acceptance test, a TDD test is not an end-to-end test. A TDD test does not interact with a live database or web server. <br> | ||
+ | |||
+ | |||
+ | |||
+ | You can do unit testing without doing test driven development. However you can't do test driven development without using unit tests.<br> | ||
+ | |||
+ | When you do traditional unit testing, you write test after you wrote your code.<br> | ||
+ | |||
+ | Test driven development approach is to write unit test before writing code.<br> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | '''How do we solve the problem by implementing STDD?''' | ||
Revision as of 17:44, 12 March 2014
OWASP Secure TDD ProjectThe OWASP Secure TDD Project allows organizations to integrate security into the Test Driven Development (TDD) lifecycle. IntroductionAbout TDD TDD is about writing a test which will fail, then writing the minimum amount of code required to make it run, then refactoring the code to make it clean. TDD is not about testing. TDD uses tests to drive the design of your code. You can do this with unit tests, functional tests and acceptance tests. Usually, you use all three. The tests tell you what to do, what to do next, when you are done. They tell you what the API is going to be, what the design is. The tests permit you to refactor safely, ensuring that the desired behavior continues to work while you adjust your design. The tests also guide you to testable code, promoting smaller methods, shorter parameter lists, and overall much simpler design than other methodologies lead you to. Difference between TDD and Unit Tests
So how does a TDD test differ from a unit test? Unlike a unit test, a TDD test is used to drive the design of an application. A TDD test is used to express what application code should do before the application code is actually written. TDD is less about testing, and more about designing the code. Unit tests are then used to set the expectations for the end code.
Like acceptance tests, TDD tests are used to drive the creation of an application. TDD tests work like mini-acceptance tests. You create a TDD test to express the application functionality that needs to be implemented next. However, unlike an acceptance test, a TDD test is not an end-to-end test. A TDD test does not interact with a live database or web server.
You can do unit testing without doing test driven development. However you can't do test driven development without using unit tests. When you do traditional unit testing, you write test after you wrote your code. Test driven development approach is to write unit test before writing code.
DescriptionWrite a description that is just a few paragraphs long Explain about the tool - VS add-on, rules engine and extensions. Explain when to use the tool - before development and when knowing the answers to business questions, e.g. user inputs
LicensingThe OWASP Secure TDD Project is free to use. It is licensed under the Apache 2.0 License.
|
What is the OWASP Secure TDD Project?The OWASP Secure TDD Project provides:
PresentationOWASP IL October 2013[1]
Project LeaderNir Valtman
Related Projects
|
Quick Download
News and Events
In PrintThis project can be purchased as a print on demand book from Lulu.com
Classifications |
- Q1
- A1
- Q2
- A2
Volunteers
The OWASP Secure TDD Project is developed by a worldwide team of volunteers. The primary contributors to date have been:
- xxx
- xxx
Others
- xxx
- xxx
As of March 2014, the priorities are:
- xxx
- xxx
- xxx
Involvement in the development and promotion of the OWASP Secure TDD Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
- xxx
- xxx
PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|