How to create a Windows Azure Web Role based application using ASP.NET MVC4 template.
- Visual Studio 2010 Pro/Express
- Windows Azure SDK 1.5 (You know, Microsoft already released the latest SDK 1.6.)
- You can get ASP.NET MVC4 from this link
1. After installed ASP.NET MVC4, you can create a new cloud application.
2. You can select ASP.NET MVC4 based Web Role as below.
3. Now you will be asked to choose ASP.NET MVC4 template as below so choose one of the given template and then select your view engine between Razor or ASPX.
4. Your project will open in VS2010 (or Visual Studio Web Developer). In the Solution Explorer windows, you will see the project details as below:
5. After it you can just launch your Windows Azure Cloud application in “Compute Emulator” by selecting Debug -> Start Debugging / Start Without Debugging.
I wrote up some test plans, but I may need to rewrite the plans depending on the answer of the following questions.
- What country is the machine going to be used in? US?
- Does it dispense cans or bottles or paper cup?
- Does the machine accept credit cards or cell phone payments?
- Does it have buttons or a touch screen?
Turns on after plugging it, and test to turn off.
Display issues (Soda machine should have the following components displayed).
- dispense button
- coin return button
- coin return dispenser
- coin slot
- bill slot
- message display
- Clicking on coin buttons should deposit appropriate amount into soda machine.
- Each coin deposited (It should increase the total amount deposited by the appropriate amount).
- Clicking on a dollar bill to deposit one dollar into the machine.
- Clicking dispense button without enough money deposited.
- Clicking dispense button with enough money deposited should dispense a pop.
- Clicking dispense button with more money that required to buy a pop should dispense pop and return any money over the amount required to buy pop.
- Clicking a counterfeit coin and bill (They should be rejected and returned immediately).
- Inserting money then pressing the coin return (total amount inserted should be returned).
- Coins return by coin return (For example, 10 coins deposited should yield 10 coins returned).
- Inserting one dollar and pressing dispense button with pop already in the dispenser – user should be prompted to remove pop from the dispenser before the machine dispenses another pop.
- When the storage rack is empty – pressing the dispense button with appropriate amount of money inserted will not dispense a pop.
- Inserted money when storage rack is empty (The money should be returned to user).
- Entering more items than the storage rack can hold (User will be prompted that there are too many items).
- Inserting one dollar and pressing the dispense button.
- Clicking dispense button with no money inserted (user should be prompted for more money and no pop should be dispensed).
- Generate a power surge of varying intensities and verify that the vending machine can handle it within specification.
- Feed bills of all denominations and make product selections as quickly as possible and verify that soda is dispensed and the correct change is returned.
- Feed change and make product selections as quickly as possible and verify that soda is dispensed and the correct change is returned.
- Use a machine to press the buttons while periodically raising the pressure until failure and verify that their failure thresholds meet specification.
- Use a machine to press the buttons with normal pressure but as rapidly as possible over several weeks and then place product in the machine and see if the buttons still function reliably.
- Verify performance while tilting the vending machine, rocking the vending machine, and hitting the vending machine and verify it functions properly.
A bug report should have:
- A detailed description of what part of the product is defective. (Description)
- Detailed data identifying the product, version, module, build, and other information to help identify exactly where the error can be found. (Environment, Version number, Feature area)
- An evaluation of the severity of the problem. (Severity)
- Customer impact descriptions include how the bug affects the user and how the problem will affect customer scenarios and requirements. (Customer Impact)
- How to reproduce the bug, with detailed steps. (Reproduction steps)
- The expected behavior versus the actual behavior.
- Attached data files/logs, test codes/scripts, or other things necessary to reproduce the bug.
- Some other information; Assignment, Bug Status, Resolution
I think one of the very best ways I can report a bug is by showing it to the Developer. I will stand them in front of my computer, fire up their software, and demonstrate the thing that goes wrong. Once they can see the problem happening, they can usually take it from there and start trying to fix it.
And, I will clarify “Customer impact descriptions” for the bug and send it to Developer and stakeholders with the bug to discuss whether we should fix it or not. Also the Customer impact descriptions include how the bug affects the user and how the problem will affect customer scenarios and requirements. Items to consider when writing a customer impact description include the following:
· Determine the customer scenarios and requirements that the bug affects.
· Determine the frequency or likelihood of the customer encountering the issue.