You are right, I am using bootstrap v 3.0, c# mvc 5.0. So, if you are calling the server, call the function to show dialog and when the call complete call the one to hide it. I added two functions to my component – show and hide the please wait. var myApp Īll I did above is mote the html into the JavaScript variable and used jQuery to call Bootstrap’s modal function. Next step is to wrap up this dialog in a reusable JavaScript component.

The black background is the default for modal dialogs in Bootstrap. So, here is how the whole thing will look. So, here is how my html for dialog looks like. I also have to make sure the user cannot dismiss my dialog manually, so I have to block keyboard. This will look very similar to Silverlight infinite progress bar. I am going to use animated striped progress bar and set its value to 100%. I am going to use two to put my “Please Wait” screen together – modal dialog and progress bar. There are many components in the bootstrap package. Typically in web applications we show this screen during server communications. One common feature that all web usually have is showing some kind of “Please Wait” dialog to let the user know that application is processing something in the background. What we have tried is marking the ContinueOnFailure property of the Step 2 in Authenticate Test to True but, wrong idea : when calling Authenticate Test within Someother Test (test as step ), ContinueOnFailure does not ignore the Logon failed step stopping Someother Test execution to step 1.Ī workaround for this could be marking Step 1 in Someother Test ContinueOnFailure property also to true but Noo, we already have tons of tests calling it and we dislike this approach.As I was working on my new web project, I decided to use Twitter Bootstrap as the foundation for my styling and components. That leads to a fail (no dialog to is found for handling) or success (Dialog is found).

Here is a short description of tests structures :Ĭurrently, in the application being tested, requirements have changed so that in the Authenticate Test, it is really needed to detect a dialog existence before handling it (step 2) : that means Step 2 can be bypassed sometimes but required some others (please, do not ask why :) ). How can I detect dialog ( Logon) existence before handling it ?

Rtwlan dialog wait it