Test-driven development (Test Driven Development, hereinafter referred to as TDD) is to ensure that code quality Air Jordan Outlet opponents, but also the consensus of the advanced program development. Apple has been committed to integration testing more convenient and available in iOS development, in Xcode 5, the new IDE and SDK XCTest introduced to replace the original SenTestingKit, and canceled the 'includes unit test' option when new construction Nike Air Max (The same treatment may also use the ARC option). The new project will automatically include the test target, and the associated frameworks set up is completed, it can be said test 579756 403 Purple White Nike Black Mamba 24 Kobe Sale finally get rid of iOS development status 'second-class citizens', and has now become as important as the adidas adiPure Crazyquick Collegiate Royal/White Q33301 Outlet product code. I believe that every engineer to complete their business code, but also have the most basic writing and maintaining the appropriate test code the obligation to ensure that their code will run correctly. Furthermore, if we can use TDD to develop, not only to ensure the correctness of code to run, but also help to arrange and ponder code structure, helping itself continues to increase. I have to test scoff at the very beginning to develop, but then many of the painful lessons of letting me know so much obsessed with the test engineers or pursuit of a more perfect test, there is a profound meaning. If you have not started writing tests for your code before you, I strongly recommend, from now on, from now on (and perhaps can not make it, please start from the next item), written tests, or try TDD development mode ʱ?? The Kiwi is a very easy to use iOS platform Behavior Driven Development (Behavior Driven Development, hereinafter referred to as BDD) testing framework, has a very nice syntax, you can write a structural strong, very easy to read the test. Because China is now information about Kiwi is relatively small, the test piece is able to add a lot of engineers who do not pay particular attention to the level of hierarchy may differ will be very far away, so in this series of two Bowen, I will first start from scratch TDD briefly introduce some concepts and ideas, and then start from the most simple example XCTest, the transition to the Kiwi test world. In the next, I will continue to introduce some depth some of the features of other higher Kiwi with a view to more developers able to reach and use this excellent Kiwi testing framework. What is TDD, why should we TDD Test Driven Development is not a very new concept. Software development engineers (of course including you and 585388-083 Anti-Nerf Nike KD V Elite Outlet me) most started learning programming, the most like to do things is to write a piece of code, and then run the observations are correct. If we do not check for errors on the return code, or join a breakpoint or output tracking program and find errors, and then run the view again it is consistent with the expected output. If the output is a simple digital console or characters that good, but if the output must be displayed on the screen at the click of a series of buttons out after things? Are we waiting compiled only once a deployment, start the program and then adidas adiPure Crazyquick Collegiate Royal/White Q33301 Outlet operate UI, it has been the point to where we need to observe it? Such behavior is undoubtedly a huge waste of a better life and brilliant youth. So some have wasted countless hours of senior engineers who suddenly discovered that we can build a similar scene in the code, and then call the code before we want to check 597806-400 Nike LeBron X EXT QS Denim-Pink Outlet in code, the result will run with our vision results were compared in the program, if consistent, then our code is not the problem, it is working as expected. For example, we want to achieve an addition function add, enter two numbers, add them together after output. Then we might imagine that 2015 Nike Free 5.0 we really have two numbers, such as 3 and 5, according to an addition within the knowledge of all ten will, we know the answer is 8. So we are compared with the prediction of 8 after the addition, if equal, it indicates that our function to achieve, at least for this example is not a problem, so we, 'this method to work correctly,' this proposition confidence increases. The example of pseudo-code as follows: // Product Codeadd (float num1, float num 2) {...} // Test codelet a = 3; let b = 5; let c = a + b; if (c == 8 ) {// Yeah, it works!} else {// Something wrong!} When the test sufficiently comprehensive and representative, we will be able to Xinxinbaopeng, boldly said, this code is no problem. We made certain conditions New Nike Free 5.0 V4 Grey Lime Trainers and assumptions, and its results for the condition to be tested using the code, and compare the expected results and the actual operation are equal, which is the basic way of software development testing. The TDD is a relative to the normal way of thinking, the more extreme an approach. We generally think of is to write business code, that is, in the above example the add method, then for writing test code, the method used to verify that the product is not in accordance with design work. The TDD thought just the opposite, in TDD world, we should first write a test case based on demand or interface, and then to write business code based on the test, but this is actually a violation of the traditional software development transcendental cognition ʱ?? But we can give a life similar examples to illustrate the necessity of TDD: Experienced bricklaying master will always pull Nike Jordan Melo B Mo a first vertical, then along the line bricklaying, because there are straight guarantee, so you can do it straight neat; and new entrants to the master often apart from anything else directly to start, and then after a stage complete with a ruler to measure the vertical and repair tools like. The benefits of TDD is not self-evident, as is always the first test, re-encoding, so all of your public at least part of the code should contain the necessary tests. Further, since the test code is to actually use the product code, so before you write production code will have an in-depth reflection and opportunities to practice how to use these codes, which Air Max 2011 Womens Grey Green improve the design and scalability have a very good help, Imagine Your tests are difficult to write an interface, someone (or yourself) to use up Mens Nike Free Run 3 Shoes Black 3 much more tangled. In the test of the criterion, you can encode purposeful direction; in addition, because of the protection of the test, you can rest assured that the reconstruction of the original code, without having to worry about damage logic. Air Max 2011 Womens Red These are actually points to a final goal: to make us happy peace of mind to work efficiently. Under the guidance of the principles of TDD, we first write test code. In this case because there was no corresponding product code, so the code is certainly not pass the test of. In most test systems, we use red to indicate Nike Free Run 3 an error, so the initial state of a test should be red. Next, we need to use the minimum price (minimal coding) to make the test pass. Testing will be represented by a green safe, so we returned to the green state. Next, we can add some test cases to verify the achievement of our product code is correct. If, unfortunately, the new test case Let us return to the red state, then we can modify the product code to make it back to the green. And so forth until all kinds of boundaries and tests are carried out is completed, then we will be able to get a guarantee with a test, robustness superior product code. In the development after us because you have these assurance testing, you can safely refactor this code or the associated code, and finally the need to ensure the project is in the green state, you can ensure that the code did not reconstruct without problems ʱ?? Simply put, the basic steps of TDD is the 'red → green → bold reconstruction.' Use XCTest to perform TDDXcode 5 has integrated testing framework XCTest (the previous version is SenTestingKit and OCUnit), the so-called testing framework, is a group so that 'will test the integration to the project' and 'preparation and practice tests' becomes simple library. Will by implementing a stack data structure example to use after initial practice what we XCTest TDD development. Everyone has some intuitive understanding of TDD later, and then go Kiwi introduction. If you are already using XCTest or other testing framework the case, you can skip this section. First, we create Nike Dunk Heels a new project with Xcode bar, select an empty project template, enter the project name in the Product Name VVStack, of course, you can use your favorite name. If you've used previous versions of Xcode, it should have noted before in this interface can choose whether to use the Unit Test, but now this box has been canceled. After the new construction, it can be found by default in the project have called VVStackTests the target, and this is when we test the use of target. Test part of the code into a default {ProjectName} Tests the group, and now there is a test file VVStackTests.m this group. Our test cases do not need to expose interfaces to other classes, so no .h file. Further general XCTest test file will do the end of the file name in Tests. Shortcuts are running tests