Update Cassini Test Technique.md

content/21.From-Audio/to-fix-transcription/Testing/Cassini Test Technique.md

@@ -1,19 +1,19 @@
-**Cassini Test Technique**
+### Cassini Test Technique
 
-One of the problems I had when I was writing tests on asp.net was to render the page. The latest version has made it better with some of the various APIs but it is still very relevant.
+One of the problems I had when I was writing tests on asp.net was to render the page. The latest version has made it better with the various APIs, but the issue of rendering is still very relevant.
 
-So, the solution was to run Cassini which Cassini is a very light weight .net web server in memory in the actual test. So basically the solution was when the test starts, you would start Cassini which is a memory, load the application, and then you would communicate with it from your tests.
+I solved my problem with rendering by running Cassini in the actual test. Cassini is a very lightweight .net web server memory. When the test started, I started Cassini, loaded the application, and then I could communicate with it from my tests.
 
-So this was spectacular because immediately it gave you full access to a writing server, the rendering was working, the the connection was working basically you just make request to the application and all the routes would work, all the views rendering would actually work and allows you to write much more interesting and powerful tests.
+This was a spectacular result because it immediately gave me full access to a writing server. The rendering worked and the connection worked. By making the request to the application, all the routes would work, all the views rendering would work, and this allowed me to write much more interesting and powerful tests.
 
-Now there was an interesting problem that occurred because the tests and Cassini were running on different app domains. So the way I solved that problem was by first of all creating a nice bridge using O2 platform but you are just using object by reference techniques and basically allowing me to actually start to talk directly to some of the or access some of the back end objects. 
+Another interesting problem occurred because the tests and Cassini were running on different app domains. I solved that problem first of all by creating a nice bridge using the O2 platform. I used reference techniques which allowed me to directly access some of the back end objects. 
 
-So I would find ways to inject stuff and connect stuff because what I really wanted was to be able to for example write a test that sees what happens with the application when you modify certain config files. So let's say you have certain config files that are likely to access some stuff and others don't how do you make sure that that is actually still working?
+So I found ways to inject stuff and connect stuff, because what I really wanted was to write a test that sees what happens with the application when you modify certain configuration files. So let's say you have certain configuration files that are likely to access some stuff, but others don't. How do you make sure the files are actually still working?
 
-So, that is a really good example of I would be able to start a test, Cassini would start and eventually we got Cassini to start literally in seconds, in fact it was milliseconds because we trimmed everything so we would just start the application with no state and then we would start to modify the config values because we exposed the config properties as much of our reference and then I would just go to the view and see what was there.
+I would start a test, Cassini would start and eventually we got Cassini to start literally in seconds, in fact in milliseconds because we trimmed everything so we would just start the application with no state. Then we would start to modify the configuration values, because we exposed the configuration properties as much as our reference, and then I would just go to the view and see what was there.
 
-So that was really, really powerful because I was able to flick the different config options and confirm that the UI and the application still behaved in that particular way. 
+So that was very powerful because I was able to flick the different configuration options and confirm that the UI and the application still behaved in that particular way. 
 
-And that sometimes, what will happen is you have all these security blind spots or all these business logic blind spots where you almost have this convention that things you work but they actually in practice don't really work or not being enforced.
+Sometimes, what will happen is you have all these security blind spots or all these business logic blind spots where you almost have this convention that things must work but they actually in practice they don't work or they aren't being enforced.
 
-So, you have these changes in settings that are supposed to determine if the user can click this or do this or perform this transaction or do this stuff directly and they are actually not enforced in the code. 
+You have these changes in settings that are supposed to determine if the user can click this, or do this, or perform this transaction, but they are not enforced in the code.