(This article also published in my public number "dotnet daily Essence article", Welcome to the right QR code to pay attention to. )
Today's articles are related to testing, outlining how to test the backend to the front-end of modern websites and applications.
Modern applications are more complex than ever, and these applications are not just for Windows, IOS, Web, Android, IoT devices, and smart watches. The composition of the application is also more complex than before, involving not only the front-end UI, but also the backend services. Without testing, it is difficult to verify that the code is working properly, and it is difficult to locate the bug where the problem is fixed. Testing typically involves unit testing of code, stress testing, acceptance testing, UI Automation testing, and so on. Unit testing not only reduces code defects but also provides documentation for your code, so you should minimize the need for unit testing and UI testing to improve the overall quality of your software when budget and effort are low.
MSDN Magazine an article on how to do it in. NET to test each end code. This article begins with a selection of test frameworks that can be selected for C #: XUnit, NUnit, MSTest, and TestDriven.NET, and for javascript: Qunit, Jsunit, and Yui test.
This article then highlights how to use Xunit to test the C # code on the server, how to test the client-side JavaScript code using Qunit, and how to automate the UI testing with Cuit (Coded UI test). The entire explanation is provided with detailed instructions, and sample code.
Although this article does not mention how to conduct acceptance testing, integration testing, system testing and other content, but in unit testing and UI testing this aspect, can be said for beginners is a very rare introductory article.
More details can be "read the original".
Original address: https://msdn.microsoft.com/zh-cn/magazine/dn973018 (en-us). aspx
End-to-end testing in modern web sites and applications