What testing tools to use?
Hi,
I am doing a research for the purpose of automating the task of unit testing, regression testing and stress testing.
The application is written as a client - server app both components written in .NET. Server is running as a service but can also run as a console app. Connects to a SQL Server 2008 database using ADO.NET. Client connects to the server using IPC or TCP remoting channel. We are not making a shift to WCF just yet.
So the question is does anyone has any experience with any testing tools? My research has led me to shortlist (purely based on their descriptions). I would welcome any other suggestions or experience with any of the tools listed below.
VS 2010 Ultimate
Testing the Application
http://msdn.microsoft.com/en-us/library/ms182409.aspx
What's New for Testing
http://msdn.microsoft.com/en-us/library/bb385901.aspx
Configuring Test Controllers and Test Agents for Load Testing
http://msdn.microsoft.com/en-us/library/ms243155.aspx
Managing Your Virtual User Licenses for Load Testing with a Test Controller
http://msdn.microsoft.com/en-us/library/ee850544.aspx
Using UI Automation for Automated Testing
http://msdn.microsoft.com/en-us/library/aa348551.aspx
Borland
Silk4Net
http://www.borland.com/us/products/silk/silk4net.html
SilkPerformer
http://www.borland.com/us/products/s...mer/index.html
AutoIt (EDIT: THIS SEEMS TO BE JUST A SCRIPTING TOOL SO OUT OF SCOPE FOR ME)
http://www.autoitscript.com/autoit3/index.shtml
IBM
Rational Functional Tester ($$$ Damn!)
http://www-01.ibm.com/software/awdto...nal/index.html
HP
Unified Functional Testing Software
https://h10078.www1.hp.com/cda/hpms/...352_4000_100__
AutomatedQA
TestComplete
http://www.automatedqa.com/products/testcomplete/
If you have any experiences with any of these then I would also love the PRO vs. CON arguments too.
TA :)
Re: What testing tools to use?
Which .net language just vb.net or other .net languages as well? You have posted multiple questions for the same question One thread will suffice.
Re: What testing tools to use?
Generally I use VS 2010 Ultimate for testing and also NUnit for unit tests.
I use sometimes Rhino Mocks for mocking or NMock or Isolator.
NCover for code coverage
generally speaking, industry standard is to use VS2010 for testing and also NUnit.
Re: What testing tools to use?
Quote:
Originally Posted by
Techno
Generally I use VS 2010 Ultimate for testing and also NUnit for unit tests.
I use those products for testing as well.
Re: What testing tools to use?
In regards to automated testing tools, they can be helpful but you need to keep on top of the scripts as in if the UI changes than so does the testing scripts for one example. Avoid writing scripts by any recording method as this relies on controls being at specific coordinates so it is best to write scripts that target controls no matter where they are on the screen. Plan on spending a good deal of time learning how to use the tools within whatever automating testing tool you select followed by how to properly writing scripts. We invested a good deal of money and time with a tool called Visual Test 6 (if I remember correctly), used it for several years but eventually stop using the tool because our testers did not see enough benefits from using any testing suite. The original testers were developers who were fine with using automation testing tools but testers that came afterwards had no background in developing apps which help lead to phasing out the use of automated testing even with using VT helping with things like stress testing that is harder to pull off without such a suite of tools for automating many users stressing out a specific application.
Re: What testing tools to use?
Wrack - people with fewer posts would be immediately banned for posting the same message in four threads. That is simply spamming. Please don't do that again without permission from the admins. Duplicate threads are being removed.
Thanks,
Brad!
Re: What testing tools to use?
My apologies Brad and to those who pointed out that I posted multiple posts. My reason was to post them in VB & C# section were many peoples who visit there don't normally visit low volume sections like testing (this is in my experience).
Again my EXPERIENCE is no excuse to spam so SORRY about that.
Now back to the topic, to give more information.
The application is written in C#. Many of the UI controls are DevExpress components along with standard .NET controls shipped with VS. We are using VS 2008 at the moment but I don't mind pushing the whole team to VS 2010 if the VS 2010 can do the job. We are not doing it because we haven't upgraded third party components just yet and the client is not willing to spend money unless necessary.
So if I understand corretly then VS 2010 ultimate would give me unit testing, regresstion testing and stress testing but not automated UI testing.
What if I were to sacrifice the UI testing bit in favour of backend methods which are called by the UI anyways. Would any of the tools I listed be sufficient?
What if I can't sacrifice the UI testing?
What about a tool that can target multi platform development (don't think these exist) like .NET, iOS, Android, Windows Phone?
Re: What testing tools to use?
Quote:
Originally Posted by
wrack
I am doing a research for the purpose of automating the task of unit testing, regression testing and stress testing.
The application is written [...] .NET. Server is running as a service but can also run as a console app. Connects to a SQL Server 2008 database using ADO.NET. Client connects to the server using IPC or TCP remoting channel. We are not making a shift to WCF just yet.
I'm sorry I'm late to the game here but can offer some helpful tips which relate both when you first posted this and are still relevant now. I'm guessing you're way beyond needing this anymore but perhaps others might find it useful here.
NUnit I'd second for unit testing. It's the first I started learning and haven't honestly needed to give any others a proper look since.
VS.Net, RFT, UFT and TestComplete I've all used personally. Pretty much most TA tools on the market are aimed at GUI testing - mimicking mouse and keyboard interaction of a manual tester or are suited to particular technologies (i.e. Selenium or SoapUI to name some other big TA vendors are more for web based testing for example). Of those you list & that I know of, these should be useable to interact with your client app, your server app as a service (at some level), your server app running in a console mode and interacting with your database.
- RFT is built on top of VS.Net so is possible for you to use
- UFT whilst using a different IDE and built with COM, has (i) plugins to interact with .Net applications and (ii) an API (read: non-GUI) mode so would most probably also be possible here
- VS.Net (ultimate, tester or Team Foundation Server level) well IS focused on .net so you could most definitely use it
For the IPC/TCP remoting RFT or VS.Net would support this as you can leverage the .net framework. UFT doesn't support this part though.
Re: What testing tools to use?
The Windows SDK contains several tools that are useful to help create accessible products and services. These tools include the following:
Accessible Event Watcher: The Accessible Event Watcher (AccEvent) tool examines accessibility data to help validate application UI elements, to ensure the UI elements raise proper Microsoft Active Accessibility and UI Automation events when UI changes occur. AccEvent is usually used to debug issues and to validate that custom and extended controls are working correctly.
Inspect: Inspect allows you to view the accessibility data in any UI element. It is especially useful, when extending a common control or creating a custom control, to ensure properties and control patterns are set correctly.
AccScope: The AccScope tool allows developers to visually evaluate the accessibility of their application during the early design and development phases. AccScope helps visualize how a screen reader uses UI Automation information that an app provides. It can show areas where adding information or support to your application can improve its accessibility.
UI Accessibility Checker: The UI Accessibility Checker (AccChecker) tool verifies that key UI accessibility requirements are met. AccChecker includes verification checks for UI Automation, Microsoft Active Accessibility, and Accessible Rich Internet Applications (ARIA). It can provide a static check looking for errors such as missing names, tree issues and more. It helps verify programmatic access and has advanced features to support automating accessibility testing.
UI Automation Verify: UI Automation Verify (UIA Verify) is a testing framework for manual and automated testing of a control's or application's implementation of UI Automation. It can also log the test results. You can integrate your application into the test code and conduct regular, automated testing or spot checks of your UI Automation scenarios. This tool is useful to verify that changes to applications with established features do not have new issues or regressions in areas beyond the new features.
Re: What testing tools to use?
Re: What testing tools to use?
I went to coaching for manual testing tools but suddenly the jobs decreased so i am in confusion to learn it or not.What you guys say? What is the future of testing tools in job market?? I am in desperate need of job.
Thanks,
Re: What testing tools to use?
Quote:
Originally Posted by
vernon750
I went to coaching for manual testing tools but suddenly the jobs decreased so i am in confusion to learn it or not.What you guys say? What is the future of testing tools in job market?? I am in desperate need of job.
Thanks,
Learn to program, and learn to test as a part of programming. There are lots of programming jobs available for people who can show they know how to code. :)
Re: What testing tools to use?
Quote:
Originally Posted by
vernon750
I went to coaching for manual testing tools but suddenly the jobs decreased so i am in confusion to learn it or not.What you guys say? What is the future of testing tools in job market?? I am in desperate need of job.
Thanks,
If you had experience with Visual Studio test with at least two or more years with testing our company in Oregon will be looking for testers in the near future. There are plenty of jobs for tester but it may depend on where you reside too.
Twenty years ago the job market was not good where I was living and moved 3,200 miles for a job which I still have so sometimes it may take a move to get a good paying job.
