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 8 years ago.
Improve this question
I have searched googles and stack overflow searching for this kind of information, but without any luck.
What I need to do, is to prepare some continuous integration server for our WP7/WP8 applications.
We need to do some unit test, and UI tests on those application, possibly on both WP7 and WP8 platforms.
Hopefully I would like to use Jenkins+Git+msbuild configuration under Windows 8 x64 Profesional.
Have anybody tried it?
Is it even possible?
Do you use real devices or emulator?
If it cannot be done with jenkins, what are the other options?
I've done it with TFS (Both Visual Studio online and on premise) and I can see no reason that it wouldn't work with Jenkins though. (Which I've previously used for other project types.)
However, the automated testing of UI is not straight forward, especially on WP7.
UI testing becomes much easier with the automated options available under WPA8.1
For 7 & 8 you could try https://github.com/Expensify/WindowsPhoneTestFramework
Be aware that you can't run the emulator on a server so UI testing there is probably not an option.
I normally run two lots of unit and integration tests.
I run "proper" unit tests in a PCL with NUnit or MSTest.
I'll run anything that needs phone integration in a test on device with https://www.nuget.org/packages/WPToolkitTestFx/
Related
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 2 years ago.
Improve this question
Understand that WebAssembly code can be executed at near-native speed across different platforms and that it can be run in modern web browsers.
Other than the above reasons (portability, performance) and perhaps security reasons, why would someone want to run their existing go/rust/c++ applications in web browsers?
Just thought that what should run in web browsers should continue to run in web browsers (i.e., javascript/typescript) and what should run on systems should continue to run on systems (Rust, Go, C/C++)
Nathan Aw (Singapore)
One reason is that they may have an application or library and they don't want to rewrite in Javascript. For example, if they have already made a game in a systems language and they want people on the web to be able to play it, they won't want to rewrite in javascript.
Javascript can be rather annoying to use in very large projects because it wasn't really designed for them. It might just be easier to write good code in a different language.
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 7 years ago.
Improve this question
I am developing a complicated project with microservice architecture (only provides Rest API). So I need to make sure that the system works stably in development, staging, and production after having a deployment.
I think that a testing framework as Frisby can help me prevent issues. Do you have any suggestion for my case?
Thank you in advance.
Definitely to prevent issues in any application there are different items to consider. For instance, one of them is having unit tests with a good coverage.
However, FrisbyJS is indeed a tool that will help to check that your services are working as expected in the scenarios specified.
Consider that if you plan to apply FrisbyJS, you will need to have some background with NodeJS, and Jasmine-node packages.
Some other alternatives:
SuperAgent, another
JavaScript library
JMeter, java application that besides
validating the functionality of your services it could also help on
testing their performance under different scenarios (i.e. specific
number of concurrent users)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am trying to start some mobile development adventure. The Windows Phone looks promising to me. But I don't want to take the wrong path.
So, what's the difference between WP7.5 and WP8 from a developer's perspective?
Will the skillset for WP7.5 still apply to WP8?
Difference? Nothing, really. The IDE is now VS2012, and you need Windows 8. The Emulator is running Hyper-V, and is a lot faster.
If you make games, you'll be have to learn DirectX instead of XNA. But for regular apps, there's no difference to the development.
You can of course use C++/CX now, should you wish it, but in reality everything is still C# 5 and XAML.
My recommendations would be to continue learning WP7, C# and XAML. Read about the new features in C# 5, specially async programming, and learn how it can enhance your development.
Right now we don't yet know the definitive details (unless someone with access to the preview SDK can expand on that) however it is unlikely that the basics will change too much.
Current standard WP7.5 apps should run on WP8 - Microsoft has said they will be centrally adjusting the apps for this compatibility.
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 8 years ago.
Improve this question
Why would I use third party testing tool like NUnit,TestDriven.Net etc, when I have Visual Studio Test System (VSTS) unit-testing framework installed?
Other testing frameworks have more features, better tool support or a different interface that some developers may prefer. For example, NUnit has the TestCase attribute allowing multiple tests to be performed using the same test method. MSTest lacks this although it is possible to emulate it (see Does MSTest have an equivalent to NUnit's TestCase?).
See NUnit vs. MbUnit vs. MSTest vs. xUnit.net for more information.
https://stackoverflow.com/a/2367759/545858
That's atleast for NUnit. And my guess is that other unit-testing tools are made because of the same reason (extensibility)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
On Windows 7, VB.NET Express, I have developed a simple Forms application. I don't really make use of any external plugins or anything - it just has a couple buttons, pictureboxes, GDI operations to modify some images...
And now it is complete. And I would like to already upload it. But, since this is actually the first time I try to submit something, what other details should I keep in mind when distributing my application? I mean stuff like... will my application work as expected in other machines? Other Windows versions? I am not in a proper position to test it in other machines, I fear, so I am relying the "default" settings and hoping it will simply work.
Unless you use platform-specific APIs (which are rare in your typical, garden-variety .NET application) then it should work on all versions of Windows that support your version of the .NET Framework. If the end user doesn't have that version of the .NET Framework installed, then he or she will need to get it manually. You can make that a little easier by using the built-in ClickOnce installer (Build > Publish <project name>) if you're not already using it.
Apart from that, no, there shouldn't be any problems, given that you say your application is a simple one. (And console applications can even work on Linux and Mac using Mono!)