-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 1
# Iteration 1 : 10th March - 24th March
We met up for the Iteration Planning meeting during which we discussed and agreed on what will this iteration consist of. With use of Poker Planning Cards, we have assigned 'points' to each task as follows;
- Selenium Web Driver and NUnit PoC (8 points)
- Database Design and Implementation (20 points)
- Save a test result to the DB (13 points)
- Dashboard
- List of tests (20 points)
- History of Individual Tests (8 points)
- Jenkins Setup (8 points)
We have come up with the user stories ourselves for this iteration, which then we included in our board.
We downloaded the Selenium Web Driver and integrated it with Visual Studio. With the use of this Web Driver we carried out some tests on several web pages. Moreover, with the installation of NUnit, we were also able to carry out assertions on these tests. From the outputted result (which could be saved and viewed in XML format) , we started to extract what variables we can use in the Database so as to show the results in a table format.
Today we have set the Jenkins server to compile .Net applications. We went through the results of NUnit (xml) to elict the fields to be used in the design of the database. We tried various scenarios with selenium to analyze changes in the xml variables; especially the asserts and results. We tried to identify the difference between failure and error. We tried to find libraries which can output code coverage results such as the NCover and the DotCover but we have decided not to implement this for now and leave only the NUnit not encapsulated by any of these libraries. We also designed and implemented the database in mySQL which we have downloaded.
We have researched on how we will be running tests with NUnit directly from our code i.e. without using the NUnit GUI to manually run the tests. Moreover, we have also started to form the Storage Procedures with regards to the Database.
We have found a way on how to run Nunit Tests directly from our code i.e with the use of the Nunit.Core Library. We have also successfully saved the test result as XML. We continued the Storage Procedures in the Database, started to practice on XML parsing with C# so as to be able to parse the test results and last but not least, we tried to acquaint ourselves with MVC in preparation for the dashboard creation.
We started to work on the XML Parser Class which goes through the XML file outputted by NUnit and extracts the information needed to be saved in the database. We also started forming the main framework and putting previously achieved work together. The Test Case Model Class was also setup to hold test case objects which are then saved to the database through the Test Database Class which we also created in this meeting. To be able to do this, the Test Database Class also was set to initialize a connection to the database. As for the Dashboard, using MVC, we succeeded in importing the database in the project and be able to show the tests available in the databse.
The Test Runner Class was customized to be able to keep backup results of the tests. The XML Parser class was integrated in the framework and test results were successfully being stored in the database. We started having problems with regards to GitHub and Jenkins and we opted for SVN which we unsuccessfully tried to set up with Jenkins.
The Dashboard was customized to be able to select a test and its test cases are shown. The Jenkins' problem was still persisting, so we tried one again to get it working the way we need it to i.e. building .NET projects. After several attempts to integrate the MSBuild plugin for our project, we succeeded in setting up Jenkins. Last but not least, the XML Parser was tested with several test cases to make sure it delivers the appropriate results.