paralell testing c# NUnit tests over Selenium grid - c#

I have been investigating paralell testing c# NUnit tests over selnium grid, and am struggling to find any recent information on how to do this.
Does anyone know whether it can be done in v2.6.3 of NUnit?
Are there code examples available?
Are there alternatives to NUnit I should consider?
My investigation so far have revealed posts going back two years or more. Some suggest its possible to do parallel testing in NUnit 2.5 or above but dont give explanations of how to achive this.
I have also come across MBUnit and PUnit, as suggestions, but again info is 2 or more years old and not very well explained.
Any help on this matter would be greadtly appreciated.

Related

Best library to generate excel and charts in excel? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 months ago.
Improve this question
Which is the best 3rd party library to use for exporting data and generating charts in the Excel from Asp.net. I have researched on .Net and found the following:
1. EPPlus: Since we are to work in a very tight schedule and the project is also not too long, so we will not be having much time to resolve issues if we get stuck somewhere after using the component. Since that is an open source library, so the time guarantee to get a help to get the issue resolved cannot be there.
2. Spreadsheetgear2012: This seems to be a good library and its site seems to show a good amount of charting examples.
3. Aspose.Cells: This also seems to be a good library and its site seems to show good charting examples although its a bit pricey, but their support seems really good and they seem very open to new ideas from clients to implement in their product and release a new version.
We are not able to take a final call whether to go for Spreadsheetgear2012 for .Net or Aspose.Cells. Any details and ideas will be highly appreciated.
The comparisons that I was able to find on internet for these products were pretty old (around 4 years back).
Our main application is online interaction and reporting from a spreadhseet, rather than generation and downloading of other spreadsheet files. We tried quite a few spreadsheet deployment options and in the end went with Spreadsheetgear. We found it to be very simple to set up, fast and flexible for this purpose. Their online examples and support are also very good.
We have moved on from their examples and have been able to set up their API with an MVC3 ASP.NET framework. It is quite a task to get it working but in the end MVC makes for a very neat code structure and much faster deployment of applications. The combination is highly recommended.
What is the most important to you? Cost, long term plan or support?
The first one is free so if cost is your biggest constraint, you really don't have options.
The second one is cheaper than your last one but it seems to have a smaller user community.
So if you run into trouble, where do you find help?
The third one provides a full series of other related products too. If you think you may need other products later, then you can bundle your existing license and that can save you money.
I am using the third one at work and think it's a good product. They have large user community and their support is responsive. But it does come with a hearty cost.
You are missing another player in this space that, while not as spiffy or as speedy to plug-and-play as the paid options, could perhaps be enough to get you where you need to go with your spreadsheets: NPOI. Even if you don't use it for your current project, it still could be worth looking into as a tool to use at a later point.
CodePlex
http://npoi.codeplex.com/
Scott Mitchell on NPOI
http://scottonwriting.net/sowblog/archive/2011/06/08/export-an-ado-net-datatable-to-excel-using-npoi.aspx
Leniel Macaferi on NPOI
http://www.leniel.net/2009/10/npoi-with-excel-table-and-dynamic-chart.html#sthash.VZ4NjvZK.dpbs
Zach Hunter on NPOI
http://www.zachhunter.com/2010/06/improved-npoi-exportdatatabletoexcel-function/

Questions and help regarding the implementation of Quartz.net 2.0

I am trying to write a simple proof of concept application implementing Quartz.net 2.x. I have never seen such poor excuse for documentation. I have so many questions that I can't seem to get answered. It seems that the documentation assumes that you have been using version 1.x and are migrating to 2.x (actually a good portion of the 2.x tutorial is 1.x specific.) Well, I've never used the Java based Quartz, Quartz.net 1.x, and obviously not 2.x. So I will try to lay my question(s) out as organized as I can. An answer to any of them or direction to documentation, a tutorial, etc. would be most welcome.
Ultimately I simply want to implement Quart.net 2.0 to fire any trivial job (embedded. not a service.)
What is structure of the job that Quartz.net executes? A method, class, etc? It seems that it is a class, but I can't seem to find a definitive answer to this question.
Can someone explain what a Factory, Store, and Datamap are and when they should be used?
What's up with the XML? Some tutorial show XML being used... some don't. When and why would I use XML?
I'll stop there for now. I hope someone has the time to help me through this. I would be very much grateful. While code is always helpful, I am more interested in understanding the process. I will need to use Quartz.net in future projects.
OK, for anyone looking for documentation, the best I could find was the Java documentation that W0lf has linked in the comments. Since Quartz.net is a port of the Java version, the documentation is similar enough to begin to understand some of the inner workings. I am developing some simple jobs to test and gain experience. Hopefully, I can contribute something to the community at some point.
Found another great place for information. The timeline starts by using 1.0 but then migrates to 2.0. But there is great info there and I can't thank the author enough for his work. Here's a link: http://jvilalta.blogspot.com
On another note, I was a little harsh on Marko Lahma. He is helping to provide an open source product that we can all use. I can't think him and his team enough for that. I do have a peeve when it comes to help requests though. It takes as much time to answer a question as it does to critique it. Why not just answer the question? Anyway, Marko, I apologize for being brash. However, finding time to update your documentation would be extremely helpful. I will contribute what I can as I can.

Which unit testing framework? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I wondered which unit testing framework would be a good one to get really familiar with? I know this might be a question of opinion, but I thought I'd ask anyways. I know that I will need to do it someday, so I might as well learn to use it. I know that there is quite a few out there, but which one is effective for C# development?
From this question I can see that unit testing is necessary, but personally I haven't used it. So that's why I ask this question.
Personally, I prefer the Visual Studio Unit Testing Framework, for two main reasons:
It integrates seamlessly with the IDE;
It's one less program to deploy in a dev environment.
Having said that, pretty much any unit testing framework will do the trick, the important thing is to have tests!
I would go with NUnit.
Some links:
NUnit QuickStart, NuGet Package
Don't get stuck on choosing a framework. Just pick one and start testing - they're not all that different. When you have written tests for a while, you will know what to look for, to suit your needs.
Personally, I have found xUnit, Testdriven.Net and Moq to be a very flexible set of test tools.
Also see this post: NUnit vs. MbUnit vs. MSTest vs. xUnit.net
I've decided to stick with NUnit because ReSharper provides native IDE support (which saves a lot of time). It's also supported by TeamCity in running and reporting automated tests.
I use NUnit for the testing framework and ReSharper for integrating it into VS (and everything else ReSharper does).
Use MbUnit (with Gallio), NUnit, MsTest or xUnit. You can combine several unit tests. I use NUnit for TDD
There are a few reasons for testing, thus a few testing environments. Plus, there are levels of testing, like simple, stubs, and mocks. For example, you could test behavior rather than state.
As far as function, I usually use the Visual Studio built in setup, add a reference to the NUnit dll, and change the c# annotations to be NUnit. This is because I like testing outside of Visual Studio, especially when it involves others on my team (and we didn't buy the team edition of VS yet).

Improve proficiency in programming [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
How can I increase my proficiency in programming? I have a grasp of the basics of C#, but don't feel too confident about my ability.
Code something in C#
Read C# Code and try to understand it.
Read a C# Book (and please none of the C# in 21 Days books)
The confidence comes with the experience.
Read Stack Overflow every day :)
Seriously. Try to solve interesting problems. Even if you don't post your solution, come back later and see if other people came up with something similar, why their solution might be different, etc.
Project Euler.
http://www.asp.net/LEARN/videos/
Voile, you are programing ASP.net.
Keep in mind that you may need a little more grasp on C# as your codes evolve. For that use a good book, most Microsoft's learn C# are pretty neat(The learn ASP.net is quite lame).
Of course, thats what I did back then(about 2 years ago), nowadays you should be able to find some awesome tutorials online.
Good luck ;)
Think of a fun project of some complexity (more that "Hello, world") and code it.
Practice, practice, practice!
Also read forums, blogs, participate in discussions. You will learn many things that aren't even mentioned in books.
read lots of code, write lots of code and keep a copy of C# 3.0 in a nutshell handy.
Learn new programming languages. Learn data structures and algorithms and design patterns. Learn regular expressions. Learn databases. Learn HTML/XHTML/DOM. Learn learn learn learn learn.
In programming, knowledge === power.
Work on something, even if it's reinventing the wheel. You can read books, watch videos and listen to podcasts all day, but the real experience comes from actually building an application. Don't build an application that you know you can build - instead, create an application that is slightly out of your reach, then rinse and repeat.
The experience when you realize that you created a mess of spaghetti code that is unmaintainable cannot really be substituted, as this then really allows you to look into techniques to improve your code. Sure, feel free to read on MSDN about Events, Delegates and Lambdas, but reading about them in the moment you need them means that the knowledge really burns into your memory.
I try to have a rough knowledge about as many topics as possible, but that's usually rather shallow: I know that a technique exists and roughly what problem it solves, so that when I need it I can learn about it.
In my opinion, the only alternative to first-hand real world experience is even more first-hand real world experience.
http://www.appdev.com/csharp.asp
:)
You say you are learning ASP.NET and C#. Have you ever done any programming or web development? Because, if you have not, then you need to take a step back and learn the basics of HTML, CSS and get a grasp of how data is passed via HTTP between client and server. I would also strongly advise getting a grounding in basic SQL, because most serious web development will utilise databases at some point.
After that, some basic OOP (Object-orientated programming) theory would do you good. That way you have a good grounding in the subject-matter before diving into the coding.
For learning C# the I'd suggest a couple of good tutorials:
The C# Station Tutorial and Softsteel Solutions C# tutorial.
I also found the ASP.NET Quickstarts useful when I was learning ASP.NET - I prefer to learn by example than by theory.
As for confidence, I'm afraid that only comes via experience. Perhaps try answering a few questions here? Getting a few up-votes might just give you that boost. Good luck.
This fits in to catagory of answers you've received thus far, but review open source projects.
Understand how they work and maybe even why they were put together in a given way. Not only will it improve your ability to write C# but it will also improve your understanding of Software Engineering which is ultimately how you put a programming language -- C# or otherwise -- to good use.
Creating a Project that makes use of a lot of different technologies is a good way to grasp a 'big picture' view.
As an example, think of an n-tier application where you input a value into a very simple web page, this value being sent into a web service, and behind that WS a simple business layer that switches between readings into a table of a data base, then you return the value finishing the output in a postback of the initial web page. In my Personal opinion, every element of the layer is a simple one, but, making the whole system work without errors is good beginner's challenge, that way you could build a confidence in your skills, enabling you to undertake any other idea.
Well, that were my two cents. Good Luck!
There may be so many projects that u can make.choose the project that makes u.it's true take a project that you consider difficult for your level.
1) analyse your project
2) define the objective
find things that are necessary to achieve the objective
3)then derive an algorithm which clearly explains the workflow
4)then start woking
In my experience "Learn By Working" is a good idea.first grab the basics then start the work soon you'll learn step by step.never give up ,be a ceaseless crusader.
practise practise it's a only way of surviving as a programmer.
Being a best programmer requires a lot of patience,thinking skills,Attention,a thrist for knowledge.
Wise people always replace the fear of unkonwn with curiosity
Actively participate in programming (and non-programming) forums.

.NET unit testing packages [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I am getting back into a bit more .NET after a few-years of not using it full-time and am wondering what the good unit testing packages are these days.
I'm familiar with NUnit (a few years ago) and have played briefly around with IronRuby, with the goal of getting something like RSpec going, but I don't know much beyond that.
I realize I could google for this and call it a day, but I believe I'm likely to get a better and more informed response from asking a question here :-)
Suggestions?
There are so many it's crazy. Crazy good, I guess.
For the conservative types (me), NUnit is still available and still more than capable.
For the Microsoft-types, MSTest is adequate, but it is slow and clunky compared to NUnit. It also lacks code coverage without paying the big bucks for the pricey versions of Visual Studio.
There's also MbUnit. It's like NUnit, but it has nifty features like RowTest (run the same test with different parameters) and Rollback (put the database back like you found it after a test).
And finally, xUnit.net is the trendy option with some attitude.
Oh, and TestDriven.NET will give you IDE integration for both NUnit and MbUnit.
I'm sure they're all just fine. I'd steer away from MSTest though, unless you just enjoy the convenience of having everything in one IDE out of the box.
Scott Hanselman has a podcast on this very topic.
Stick to NUnit. Don't go anywhere near MSTest.
NUnit + ReSharper is an absolute joy to work with.
We use NUnit and MbUnit here. We use TestDriven.NET to run the unit tests from within Visual Studio. We use the excellent, highly recommended RhinoMocks as a mock framework.
I used to use NUnit, but now tend to use MbUnit, for two key features:
1. The RowTest feature allows you to easily run the same test on different sets of parameters, which is important if you really want thorough coverage.
2. The Rollback feature allows you to run tests against your database while rolling back changes after every test, keeping your database in exactly the same state every time. And it's as easy as adding the [Rollback] attribute.
Another nice aspect of MbUnit is that its syntax is nearly identical to NUnit, so if you have a whole test bed already in place under NUnit, you can just switch out the references without the need to change any (very much?) code.
xUnit.net looks like it provides a slightly different approach to NUnit, MbUnit, and MSTest, which is interesting.
In my search for an RSpec-like solution (because I love the RSpec), I also came across NSpec, which looks a bit wordy, but combined with the NSpec Extensions addon to use C# 3 extension methods, it looks pretty nice.
I use the following:
TestDriven.NET - Unit testing add on for Visual Studio
Typemock Isolator- Mocking framework for .NET unit testing
NUnit - An open source unit testing framework that is in C#.
You might find it interesting that Gallio v3.1 now supports RSpec via IronRuby.
I like TestDriven.NET (even though I use ReSharper) and I'm pretty happy with XUnit.net. It uses Facts instead of Tests which many people dislike but I like the difference in terminology. It's useful to think of a collection of automatically provable Facts about your software and see which ones you violate when you make a change.
Be aware that Visual Studio 2008 Professional (and above) now comes with integrated Unit Testing (it used to be available only with the Team System Editions) and may be suitable for your needs.
I used to use NUnit, but I switched to MbUnit since it has more features.
I love RowTest. It lets you parametrize your tests. NUnit does have a little bit better tool support though. I am using ReSharper to run MbUnit tests. I've had problems with TestDriven.NET running my SetUp methods for MbUnit.
NUnit, MSTest, etc. all do pretty much the same thing. However, I find NMock indispensable.
NMock or any mocking package is not unit testing, but it makes it so much easier to do unit testing that it might as well be.
I like MbUnit, er, Gallio. Most importantly to me is having good tools support inside Visual Studio. For that I use Resharper, which has an MbUnit test runner. A lot of folks seem to like TestDriven.NET as their test runner as well.

Categories