Things are not my concern. Therefore, in the render method, you only want to use the JSX conditional character to display posts when the array is not empty. My entire component includes: Before discussing how to change the status test data of reaction components into status with enzymes, please check whether it works normally after execution. One at a time. One of the benefits of enzymes is that they can change the state directly or read the state of components. The
In fact, this means that you can test whether the component works when you add a post to a state without worrying about how to add a post to the state. It was an additional complication that we arrived as soon as we were ready. The first two to test are. State Loop how to publish and state when posts is not empty. When posts is empty, no error is generated and nothing is displayed. Enzyme provides the setstate method, which allows you to call the setstate method of the class in the test. This class is the top level of program state management, so it must be designated as a black box here. Let’s look at a test that adds posts to the state and ensures that they are rendered correctly. This is very similar to the previous tests on the posts component. Verifying that works properly in this context. Suppose you want to add the ability to use enzymes to call react class methods to edit a post using the application. The postedit component already exists. But we must supply it to the right position. To track the ID of the post you are currently editing, let’s add a property to state. State You don’t want to copy a post from posts, just the ID. Finding posts in status is a separate issue and uses a unique approach. Let’s look at the creator and the new method. Note how to explicitly bind the generator’s this to the method’s this using the binding function in the generator. If not, this one. State, this Setstate and this. Props undefined. This is an additional step that must be performed for all individual methods in a class that uses props or state. You can then use this component and the postedit component in rendering. To test this feature – we will add a dew test to find the correct post and display it when the editor finds the post. Each is based on the last one. The last test was post. Since state is discussed, you can safely do the same and test the following steps: Once you believe it works (trust me, in the first version of this method, the test failed.) When the status indicates, you can go to the test displayed in the editor. This test demonstrates that editors are available when needed. Does not show when the editor should not be shown without proof. Therefore, the test itself may be a false positive. In order to prove that it is not a false positive, other possibilities need to be tested. Test the impact of the realt change handler on the status. If you finally need to drag the series to other 3-4 posts. Add a component that updates the post you want to update and connect to this application component. To do this, you need a change handler for the state of the application component. After the component’s change handler is invoked, we will add and test it to see an example of how to test the state. To control values, separate and test the change control slider before implementing the component, which means that the control is designed around interface requirements, not the opposite. In addition, the control can be interchanged,
As long as we work together, we don’t care what it is or what it will become. Here is a simple change handler function: Can be passed to the control. The following is a test that calls the method directly and then tests the state using the state method of enzyme. How about loading a post? You need to actually add a post at a certain point in time. I say again, the complex is left to state management. However, to encapsulate all the content of the application, you need classes to take advantage of realt lifecycle events. Realt lifecycle events are the same as WordPress operations. This is the opportunity to run code at a specific location where the program is running. The earliest or component can safely perform Ajax requests on the data, and the update status is componentdidmount. Event that occurs when a component is loaded into the dom. The status cannot be updated before this event. I think API requests should be handled by Redux or other state management systems. This approach means that API interaction is strongly integrated into UI components, which reduces the possibility of reuse, and API clients cannot be reused in testing or unresponsive. Test led response development I want you to remove two from this series. The first approach is to use testing to lead development, determine what is simple and actionable, and then slowly add complexity. For me, this means developing one small functional unit at a time. Easy to think and work. I like it. Another important aspect is not to overuse react class components. Maximum use of stateless storage components can reduce complexity, increase reusability, and make functional components easier to test than class components. Most importantly, we hope to see how react can help us follow this practice, because it clearly defines the value of isolating problems and the benefits of the software design and react. The following article will discuss the realt component sharing between Gutenberg and realt.
