haorusong

The most valuable thing you can get out of any book is a list of other books worth reading. Over time, you will find that certain books keep popping up from the "bibliography", and you should move those books to the top of the reading list. Other books will sink. Since the reading list is essentially a priority queue, you'll eventually find that some books sink so far down the queue that you may never read them again. Start by picking a broad book to give you a general idea of the subject you are aiming for. Then choose a few specific books to master the aspects of the topic that interest you. Reading the right book at the right time will have a better effect. A lot of reading can improve your reading ability. You will also improve your knowledge of the outside world through reading. For computer science, reading a lot of the latest information will be of great help to your future work and research. Reading will improve your horizon and enrich your spare time. Even if you...

 Mockito is a Mock framework for Java single-testing, but it can also be used with other single-testing frameworks in addition to JUnit. Mockito changes the behavior of a class or object, allowing us to focus more on testing the code logic without the effort of constructing the data. The basic concept Mocks can be of two types, Class and Partial，so Mockito is called spy. The behavior of changing methods on mock objects is called Stub. A Mock process is called a Mock Session, and it records all the Stubbing. It consists of three steps: +----------+ +------+ +--------+ | Mock/Spy | ===> | Stub | ===> | Verify | +----------+ +------+ +--------+ Class Mock A Class Mock changes the behavior of a Class so that the object it mocks completely loses its original behavior. Method returns default values (null, false, 0, etc.) if it is not pegged. The most basic usage is as follows: 1 2 3 4 5 6 7 8 9 10 11 12 import static org.mockito.Mockito.*; // use List.class to...

 When working on an open-source project, please get in the habit of downloading the latest version of the code (preferably from their source control system), so you can review its history and track future developments. Please take a look at the codebase structure and think about why it is organized the way it is. Look at how developers manage their code modules to see if it makes sense and compare them to how they might have used them. Try to refactor the code to understand why its coders made the decisions they did, and think about what the code would look like if you were the one coding it. It will give you a better understanding of the projects; Also, make sure you can build those projects. If you've found a better way to do something, you're ready to contribute code to the project. Inevitably, as you go through the code, you'll come across decisions you completely disagree with it. Ask yourself if the developers of the project might know something you don't or vice ...

 Links to evidence of activity on GitLab. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/generatewcfbreportfrontend I created a new generate WCFB report frontend which I used the sample frontend example from the professor. I have already had a basic model for the Frontend. I need to do more to connect the backend API, which can let customers download the report for the inventory. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/23 I designed the API for backend endpoints. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/34 I met with Marcos and Matt and talked about the difference between each group's FrontEnd design. For the next sprint, we will be having more meetings to help each other out on the API. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/35 I looked for WSU visual standards to use fo...

 We can all benefit from writing random "toy" programs to push ourselves to the limit by setting artificial limits. -- Donald Knuth, The Art of Computer Programming If you can learn as much from failure as you can from success, you need a relatively private space to look for the loss. In balling acrobatics, a performer who tosses three balls will never progress if he has never tossed five. Those who spend hours picking dropped balls until their back hurts eventually get good at it. The same lesson applies to software, where software workers often need to step out of their comfort zone to try something they're not good at it. It is by taking bold chances again and again that you improve your skills, that you learn and grow from failure after failure. Just as a three-ball-tossing performer does not throw five balls in a formal performance, software developers often make mistakes in new areas. Software developers also need a safe place to make mistakes. It's terrible not...

Structural testing is based on the source code of the program under test, rather than the definition. This is known as white box testing, while functional testing is known as black-box testing. Program diagram: For a program written in an imperative programming language, the program diagram is a directed graph with nodes representing statement fragments and edges representing control flow. DD - path DD path: Decision-to-decision path (Miller). Begin with the "exit" of the decision statement and end with the "path" of the next decision statement. DD chain: A path of starting and ending nodes at different points in a directed graph. Consisting of a node, the internality =0; Consisting of a node, externality =0; Consisting of a node, the inner degree > =2 or the outer degree > =2; Consisting of a node, the degree inside =1 and the degree outside =1; Length > =1 for maximum drill DD - path graph A DD-path graph is a labeled directed graph in which nodes represe...