Hence, I implemented this feature. This will be available in XStudio 1.0b1.
Wednesday, October 21, 2009
XStudio 1.0: Browser-like Previous/Next buttons
With the introduction of some anchors in different parts of XStudio, the user is often redirected to one specific node of one specific tree. It was then becoming to be able to go back and forth through the history and navigate like within a browser.
Hence, I implemented this feature. This will be available in XStudio 1.0b1.
Hence, I implemented this feature. This will be available in XStudio 1.0b1.
XStudio 1.0: Inheritance of the attachments
Starting from XStudio 1.0b1, attachments are inherited through their whole hierarchy. For instance, if you attach a file (i.e. a mockup design) to a requirement, you will be able to see in this requirement's "attachments" tab not only this attachment but ALL the attachments associated to his ancestors (parent folders and category).
Of course, you can directly open or download the attachment from any of the ancestor nodes but you can also move directly to one of these parent by clicking on the anchors:
Of course, you can directly open or download the attachment from any of the ancestor nodes but you can also move directly to one of these parent by clicking on the anchors:
Website updated
The website (http://www.xqual.com) has been updated to support all the popular browser:
- Firefox 3+
- IE7+
- Safari
- Opera
- RSS
- Blog
- StumbleUpon
- MySpace
- Digg
- Delicious
- Google Bookmarks
- Reddit
Wednesday, October 14, 2009
Release of XStudio 1.0a4
The version 1.0a4 of XStudio has been released and is available for download at the usual location: http://www.xqual.com/support/download.html.
Main changes from 1.0a3 are:
* Coverage metrix on campaigns (full and partial)
* Coverage metrix on campaign sessions (full and partial)
* Coverage metrix on category (req + spec + test)
* Coverage metrix on folders (req + spec + test)
* Automatically create testcases if the launcher is requesting it
* Progression/Regression metrix on campaign
* Bug-fix:
- Percentage rounding in coverages
- Dependency graph modality problems
- VisualStudio launcher results parsing finally implemented
I also worked on:
* New website (http://www.xqual.com) supporting perfectly IE7+, Firefox3+, Chrome and Safari
* New open-source section (GPL3) on the website containing all the launchers
* Initiation of teh development of automated functional tests on:
- the XStudio NSIS installer (using the AutoIt launcher)
- the XStudio Java unit testing (using the JUnit4 launcher)
In addition, I developed a bunch of new launchers for XStudio:
* Froglogic Squish for Qt
* Froglogic Squish for the web application
* Microsoft Visual Studio Team System
* Jalian Marathon
* Beanshell
* JUnit v3
* JUnit v4
* PyUnit
* NUnit (.NET)
* TestNG
Main changes from 1.0a3 are:
* Coverage metrix on campaigns (full and partial)
* Coverage metrix on campaign sessions (full and partial)
* Coverage metrix on category (req + spec + test)
* Coverage metrix on folders (req + spec + test)
* Automatically create testcases if the launcher is requesting it
* Progression/Regression metrix on campaign
* Bug-fix:
- Percentage rounding in coverages
- Dependency graph modality problems
- VisualStudio launcher results parsing finally implemented
I also worked on:
* New website (http://www.xqual.com) supporting perfectly IE7+, Firefox3+, Chrome and Safari
* New open-source section (GPL3) on the website containing all the launchers
* Initiation of teh development of automated functional tests on:
- the XStudio NSIS installer (using the AutoIt launcher)
- the XStudio Java unit testing (using the JUnit4 launcher)
In addition, I developed a bunch of new launchers for XStudio:
* Froglogic Squish for Qt
* Froglogic Squish for the web application
* Microsoft Visual Studio Team System
* Jalian Marathon
* Beanshell
* JUnit v3
* JUnit v4
* PyUnit
* NUnit (.NET)
* TestNG
Wednesday, October 7, 2009
XStudio 1.0: Automatically create the default testcase
In some specific cases, the notion of testcase is useless. For instance a JUnit test will match one test class. This test class can run several methods which could be identified to testcases. The problem is that it is impossible to run only one single method within a JUnit class (using the console runner JUnitCore).
However, without testcase, XStudio will not execute anything. So, the user would need to create one fake testcase for each test. Hence, the launcher would ignore the testcase index, would execute the test including all its methods, retrieve the results, traces etc. and store all this in the fake testcase. But creating a default testcase manually for each test is a bit painful and unnecessary from a user point of view.
In these cases, the launcher can now call (i.e. in the initialize() method) the method setDefaultTestcaseMustBeCreated(true). This will automatically create a default testcase at runtime if no testcase exist.
However, without testcase, XStudio will not execute anything. So, the user would need to create one fake testcase for each test. Hence, the launcher would ignore the testcase index, would execute the test including all its methods, retrieve the results, traces etc. and store all this in the fake testcase. But creating a default testcase manually for each test is a bit painful and unnecessary from a user point of view.
In these cases, the launcher can now call (i.e. in the initialize() method) the method setDefaultTestcaseMustBeCreated(true). This will automatically create a default testcase at runtime if no testcase exist.
Tuesday, October 6, 2009
XStudio 1.0: New famous launchers are ready
Since I'm almost ready with the features of XStudio v1.0, I started working on some famous launchers people will like:
- Beanshell
- Froglogic Squish for Qt
- Froglogic Squish for Web
- JUnit v4
- JUnit v3
All are implemented and just need a little bit more of testing.
An example of integration with JUnit v4:
All the results/messages are detailed enough and include the major information from the JUnit console messages.
In addition, the complete output from JUnit is stored as an attachment to the testcase, so that the user can get the complete log if necessary:
I'll also work on a launcher for SQL and possibly CUnit this week.
- Beanshell
- Froglogic Squish for Qt
- Froglogic Squish for Web
- JUnit v4
- JUnit v3
All are implemented and just need a little bit more of testing.
An example of integration with JUnit v4:
All the results/messages are detailed enough and include the major information from the JUnit console messages.In addition, the complete output from JUnit is stored as an attachment to the testcase, so that the user can get the complete log if necessary:
I'll also work on a launcher for SQL and possibly CUnit this week.
Saturday, October 3, 2009
XStudio 1.0: New progressions/regressions statistics
A new "Statistics" tab will be present on any campaign on XStudio 1.0a4.
The information are taken from all the sessions executed belonging to the campaign. All the results are put in a graph so that the evolution (progression or regression) in time is clearly visible. The last session's results are also displayed.The new tab is split in 2 tabbed panes: one that shows the evolution of tests results and another one going deeper at the testcase level.
This feature will be available in XStudio 1.0a4 at the usual location http://www.xqual.com/support/download.html (probably in just a few days).
The information are taken from all the sessions executed belonging to the campaign. All the results are put in a graph so that the evolution (progression or regression) in time is clearly visible. The last session's results are also displayed.The new tab is split in 2 tabbed panes: one that shows the evolution of tests results and another one going deeper at the testcase level.
This feature will be available in XStudio 1.0a4 at the usual location http://www.xqual.com/support/download.html (probably in just a few days).
Thursday, October 1, 2009
XStudio 1.0: New coverage metrics
XStudio 1.0a4 (that was not planned but hey I'm a bit ahead of time so...) will include a new great feature that I've just finished to develop: in addition to all the already existing coverage metrics provided, some new ones will appear in the next version. Coverage from ANY folder in the requirement or specification trees (this allows to refine metrics on one particular node in the tree) and detailed coverage on campaigns and campaign sessions.
Specification tree:
How many specifications under the selected folder are covered by some tests.
Of course, you can get the details of which specifications are covered and which are not.
Coverage of a campaign:
Since a test campaign is by definition a group of test, we can now also get the following metrics:
- Specifications fully covered by the campaign
- Specifications partially covered by the campaign
- Specifications not covered by the campaign
- Requirements fully covered by the campaign
- Requirements partially covered by the campaign
- Requirements not covered by the campaign
Coverage of a campaign session:
On the campaigns, all the data data were global (based the complete set of requirements and specifications). We can get some even more interesting data on campaign sessions since the session is associated to a SUT (and an SUT is associated to a list of requirements).
Hence, we can again refine the information and get the following metrics:
- Specifications associated to the SUT fully covered by the campaign
- Specifications associated to the SUT partially covered by the campaign
- Specifications associated to the SUT not covered by the campaign
- Requirements associated to the SUT fully covered by the campaign
- Requirements associated to the SUT partially covered by the campaign
- Requirements associated to the SUT not covered by the campaign
This allows to know precisely if some tests are missing in the campaign, or if some associations between requirements, specifications and tests are missing.
I think those new features are great tools to help analyzing what you're testing and more importantly what you're missing. They will be available in XStudio 1.0a4 at the usual location: http://www.xqual.com/support/download.html.
Specification tree:
How many specifications under the selected folder are covered by some tests.
Of course, you can get the details of which specifications are covered and which are not.
Requirement tree:
How many requirements under the selected folder are covered by some specifications.
How many requirements under the selected folder are covered by some tests (through specifications).
Of course, you can get the details of which requirements are covered by some specifications and which are not but also which requirements are covered by some tests.
How many requirements under the selected folder are covered by some specifications.
How many requirements under the selected folder are covered by some tests (through specifications).
Of course, you can get the details of which requirements are covered by some specifications and which are not but also which requirements are covered by some tests.
Coverage of a campaign:
Since a test campaign is by definition a group of test, we can now also get the following metrics:
- Specifications fully covered by the campaign
- Specifications partially covered by the campaign
- Specifications not covered by the campaign
- Requirements fully covered by the campaign
- Requirements partially covered by the campaign
- Requirements not covered by the campaign
Coverage of a campaign session:
On the campaigns, all the data data were global (based the complete set of requirements and specifications). We can get some even more interesting data on campaign sessions since the session is associated to a SUT (and an SUT is associated to a list of requirements).
Hence, we can again refine the information and get the following metrics:
- Specifications associated to the SUT fully covered by the campaign
- Specifications associated to the SUT partially covered by the campaign
- Specifications associated to the SUT not covered by the campaign
- Requirements associated to the SUT fully covered by the campaign
- Requirements associated to the SUT partially covered by the campaign
- Requirements associated to the SUT not covered by the campaign
This allows to know precisely if some tests are missing in the campaign, or if some associations between requirements, specifications and tests are missing.
I think those new features are great tools to help analyzing what you're testing and more importantly what you're missing. They will be available in XStudio 1.0a4 at the usual location: http://www.xqual.com/support/download.html.
Subscribe to:
Posts (Atom)