![]() ![]() # THIS SOFTWARE AND DOCUMENTATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND # CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A # PARTICULAR PURPOSE ARE DISCLAIMED. # * Neither the name of the copyright holder nor the names of its # contributors may be used to endorse or promote products derived from # this software without specific prior written permission. # * Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # Redistribution and use in source and binary forms of the software as well as # documentation, with or without modification, are permitted provided that the # following conditions are met: # * Redistributions of source code must retain the above copyright notice, # this list of conditions and the following disclaimer. # Copyright (c) 2010 by the Pallets team. The # Flask license statement has been included below as attribution. """ # The following function is derived from an example in the Flask documentation # found at the following URL. Import pytest from culturemesh import app """Initialize the testing environment Creates an app for testing that has the configuration flag ``TESTING`` set to ``True``. The code those tests cover is likely where the bug is If you make a change that breaks your program, you can check which ![]() docstrings or javadoc), and it is the kind of testing that can help ![]() Is the kind of testing that can replace many of those function-level comments Unit testing has benefits besides bug-catching, though. We hope that across all three types of testing, nearly all theīugs will be caught. This doesn’t mean that unit testing isn’t useful though, just that it’s not a The program interact, and it is quite time-consuming to actually test each part Of course, this is incredibly optimistic. Therefore, we write tests to verify that each piece–each When we put the pieces all back together, the program should also behave asĮxpected. If we are sure that each little piece behaves as expected, then Break the program into all its little pieces, each of which has well-definedīehavior. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |