Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN/TFS/WPF/CodePlex ProjectDNN/TFS/WPF/CodePlex Project
Previous
 
Next
New Post
1/23/2008 11:16 PM
 

Hey everyone, 

I'm taking on a multi step endeavor to try some "theories" of automatic release management/QA/UAT utilizing DNN (sorta).  I say theroies because it's a bit scattered right now, but I do have a grand vision, I just don't know how to fully explain it.

I have started a codeplex project for it, http://www.codeplex.com/yakshaver .  I will be developing a system to work similar to the DNN release tracker (with a few changes based on wild ideas) in conjunction with TFS/CodePlex. 

What am I looking for?  Anyone that wants to help of course, but if anyone has some WPF (or for that matter *wants* some) and/or Windows Control hosting experience then sign on up. 

My goal is to provide a system that will allow:

1) Testing Exposure - Get *anyone* to test your software/modules and provide useful information without having to do a lot of work.  Reduce the # of steps it takes to record a bug/request a feature/file a complaint/whatever.  I think with WPF and of course any # of communiations structures we can build a user control that allows this to be done.  Well, I know we can. 
2) Sandboxing / Multiple QA environments - in promotion of Agile, allow QA to publish builds at their leisure and make it as automated as possible.  Also provide tools for validating that the envirnment was proper established. 
3) Provide valuable information to a more powerful management system - I'm not going to rewrite TFS or CodePlex.  They can perform metrics on work items, change sets, etc, this will help dump more data in there for more accurate results.  
4) Help Desk / Knowledge Base - Really don't know a lot about either of these, but think it would be awesome to take lessons learned or bug resolution/work arounds and publish it to something more common.

This is a very high level view, a short example of what I would like to accomplish, I have a lot more detail available and will continue to do so.  I would like to use a real DNN module (perhaps a core module) and move it to codeplex (not necessarily *officially*, but something to give value, Like MAnnouncments or something to that effect).  Accomplish everything from automated release publishing, to validation of entrance and exit criteria (automate tasks that we can, like validating a package, a tool that could be used by *many* dnn developers).  I'll keep it short on here, but hopefully some of you see where I'm going.

Sorry for my rant.  If your interested drop me a line.  I think it will be a fun project, and maybe we could build something really useful to the developer community. 


------------- w00t!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN/TFS/WPF/CodePlex ProjectDNN/TFS/WPF/CodePlex Project


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out