Databases
StackOverflow2013
Postsdbo
POAm I writing my first MSpec specifications correctly?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAm I writing my first MSpec specifications correctly?
    primarykey
    data
    text
    <p>I'm writing my first MSpec specifications and I wanted some guidance. I left the specs in the "pending" state, but the context is filled out. Are there any improvements to be made?</p> <p>For reference, this is the story and first scenario: </p> <pre><code>Story: "Blog admin logs in to the system" As a blog writer I want to be able to log in to my blog So that I can write posts and administer my blog Scenario: "Logs in from the login page" Given the user enters in correct credentials for a user in the system When the user clicks the "Login" button Then log the user in and redirect to the admin panel with a message stating that he logged in correctly </code></pre> <p>And the MSpec code (some parts snipped), notice that I had to alias the MSpec <code>It</code> delegate due to a conflict with <code>Moq.It</code>:</p> <pre><code>using MoqIt = Moq.It; using ThenIt = Machine.Specifications.It; [Subject("User tries logging in")] public class When_user_enters_valid_credentials : With_user_existing_in_membership { protected static ActionResult result; Because of = () =&gt; { result = loginController.Login(validUsername, validPassword); }; ThenIt should_log_the_user_in; ThenIt should_redirect_the_user_to_the_admin_panel; ThenIt should_show_message_confirming_successful_login; } public abstract class With_user_existing_in_membership { protected static Mock&lt;ISiteMembership&gt; membershipMock; protected static string validUsername; protected static string validPassword; protected static LoginController loginController; Establish context =()=&gt; { membershipMock = new Mock&lt;ISiteMembership&gt;(); validUsername = "ValidUsername"; validPassword = "ValidPassword"; //make sure it's treated as valid usernames and password membershipMock .Setup&lt;bool&gt;(m =&gt; m.Validate( MoqIt.Is&lt;string&gt;(s =&gt; s == validUsername), MoqIt.Is&lt;string&gt;(s =&gt; s == validPassword))) .Returns(true); loginController = new LoginController(membershipMock.Object); }; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAnthony Mastrean
    1. USSekhat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USSekhat
      1. VTBountyStart
    2. VO
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USmatma
      1. VTFavorite
    3. VO
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USalexfgo
      1. VTFavorite
    1. COYeah, I see you have the same issue with the Moq framework and MSpec framework that I did. How "It" is defined in both. Doh. Hehe. +1 for asking the question, I am doing this EXACT thing but see it was answered a while ago.
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USeduncan911
    2. COyou may want to look at NSpec (www.nspec.org). NSpec does a better job of not colliding with name collisions such as this. It handles context build up a little differently (you dont have to create a separate class to set up a context).
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USAmir
    3. COWell colliding names aren't a problem, that's the entire point of giving you Aliases. But I'll give it a look anyway.
      singulars
      1. POAm I writing my first MSpec specifications correctly?
      1. USSekhat
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload