This project is read-only.
  1. Browse to http://dotnetnukeautomation.codeplex.com/
  2. Click on Source Code
  3. Download the latest version
  4. Open SQL Server Management Studio (do not connect using SQL Express)
  5. View the properties for the server you will be using for the test
  6. Enable SQL Server Authentication under the Security Page
  7. Close SQL Server Management Studio
  8. Create a folder called tests
  9. Within Tests, create five sub-folders: Databases, Packages, Websites, TestEmails, Screen Captures
  10. Add the DNN install package that will be tested to the Packages folder
  11. Multiple packages can be added, including both Community and Professional packages
  12. Add the DNN Upgrade Package that will be tested to the Packages folder
  13. Add the test bed packages that you will be running upgrades against to the Packages folder
  14. Create a folder for the Automation project
  15. Extract the source code to the folder you created
  16. Navigate to projectLocation\ DotNetNuke.Tests.UI.WatiN.BuildVerification and open the app.config (in VS or a text editor)
  17. Update the “TestRoot” value to reflect the location of the tests folder you created (ex. C:\Tests)
  18. Update the “TestFilesPath” value to reflect the location of your project projectLocation\ Test Files
  19. (Optional Step) Add an alternative language package to the Test Files folder
  20. Update the “LanguagePackage” value to match the new package you added (make sure the value includes the .zip ending)
  21. Update the “LocalName” value to match the local name of the language you will be using
  22. Open the Project solution (DotNetNukeWatiNTests.sln ) in VS 2010 (or other)
  23. Open the InstallList.csv File (projectLocation\ DotNetNuke.Tests.UI.WatiN.BuildVerification\TestData) edit the list of install tests that will be run, save the file and build the solution.
  24. Entries are in the format “”, “Install type” For Example: “”, “Auto”
  25. The blank quotes are needed to match the format of the entries in the upgrade list
  26. Open the UpgradeList.csv File (projectLocation\ DotNetNuke.Tests.UI.WatiN.BuildVerification\TestData) edit the list of upgrade tests that will be run, save the file and build the solution.
  27. Make sure that the upgrade packages for any upgrade tests you wish to run are in the packages folder
  28. Entries are in the format “UpgradeSiteVersion”, “UpgradeSiteType” For Example: “04.09.03”, “2”
  29. The upgrade site type value refers to the type of test bed you are using. Test beds have been created for some versions with multiple types (i.e. different set ups) the type is indicated by a number in the .zip file name (ex. DNN4932.zip)
  30. Professional Edition test sites are numbered similarly but they also include “Pro” at the end, if you are testing a professional test bed you will need to include the “Pro” so the tests will be able to find the correct zip file. For example if I wanted to use test site DNN5232Pro.zip the entry in the upgrade list would be: “05.02.03”, “2Pro”
  31. Click on Test->Windows-> Test List Editor
  32. Check any tests that you wish to run
  33. Click the run button within the editor


Additional Notes:
Any non-upgrade or install tests require both an install and upgrade database and website to have been created already, these will be created when you run the install and upgrade tests as part of the tests. This means that when you run tests on a version for the first time you will have to include both the “InstallShouldSucceed” and “UpgradeShouldSucceed” tests. Once these have been run against a version successfully you do not need to always include them in the tests you run.
The “InstallShouldSucceed” and “UpgradeShouldSucceed” tests will be run for each entry in their respective List files. This means that if your InstallList.csv file has all three possible entries:
"", "Auto"
"", "Typical"
"", "Custom"

Then your install test will run three times, once for each install type and three separate websites and databases will be created. Each non-install/upgrade test will also run three times, against each of the sites created in the install tests.
This is the same for the “UpgradeShouldSucceed” tests. For example if you have five entries in the list then the upgrade tests and non-upgrade/install tests will run five times against each of the upgrade types.
"04.09.03", "1"
"04.09.03", "3"
"05.00.00", "2"
"05.02.01", "1"
"05.03.00", "1"

Last edited Sep 14, 2010 at 11:12 PM by philipbeadle, version 6

Comments

No comments yet.