simulator or test environment for web application - testing

I am working on a web app that will run only on firefox and on win / linux machine.
I have done that thing and now want to test with various environment like mac, android, opera browser etc.
My query is whether there is any test environment (simulator) available that will allow me to test the app on different platform without testing on real machine?
Thanks to all

You could give a try with a virtual machine like VirtualBox / VirtualPC / VMWare.
Some Windows versions are available freely as virtual machines images in the Microsoft site.
Not sure for the rest , as you write first
a web app that will run only on firefox and on win / linux machine.
...but then talk about mac and android.
For android, you could give a try with their emulator.
For Mac OS I am afraid that you won't find legal solutions.

Related

Ideas on how to get around Windows 11 ARM not supporting IIS

My new Macbook Pro running on an M1 Max (ARM) chip just came in. I installed Parallels and Windows 11 Preview for ARM, and Visual Studio installs / launches / builds my solution beautifully. Unfortunately the turn windows features on or off dialog doesn't have the option for installing IIS, and others have posted that this is not supported in Windows 11 for ARM.
Our dev team runs multiple ASP.NET Core 3.1 websites locally under IIS using subdomains, e.g.: https://auth-dev.mydomain.com, https://web-dev.mydomain.com, https://webapi-dev.mydomain.com. This was easy to set up in IIS using the bindings dialog, I could specify for port 443 (https) to use a certain subdomain and our dev SSL certificate.
Now I need to figure out how to make this work on Windows 11 ARM. Developing on an inferior non-Macbook Pro laptop doesn't seem like a great solution for .NET devs, I have to assume others with M1 chip Macbook Pros have run into this same issue. What are my options?
I first started looking into using IIS Express, but it seems like every website has to run on a different port, whereas I need them all to run on port 80 (just with different subdomains.) I'd be fine with them running on different ports if there was a way to forward those various ports to the subdomains, but it doesn't seem like the windows HOSTS file supports that.
I also looked into using the Apache web server for Windows, but I read somewhere that it doesn't support running ASP.NET Core apps.
OS build 22563.1 supports IIS. I'm not sure if this is the first build that supports it, but I checked after the last automatic windows update and the IIS features are available; they were not before. I am on a m1 Mac using Parallels with the Windows Insider Preview ARM image.
Edition: Windows 11 Pro OS
Build: 22563.1
Experience: Windows Feature
Experience Pack 1000.22563.1.0
I'm using Windows 11 & IIS Express on a MacBook Pro M1 Max (via Parallels) and it is working fine. Of course, for developing environment!
You can download IIS Express from
https://www.microsoft.com/download/details.aspx?id=48264
You can download the ASP.NET Core Runtime or .NET 5.0 SDK to allow you run to run ASP.NET applications on Windows, Mac or Linux.
See https://support.microsoft.com/en-us/windows/downloads-for-windows-32490f9b-01ee-c13e-b2af-b5057c2d34e8

Test application on multiple desktop platforms

Does anyone know of a website that allows me to create virtual machines with various versions of Windows, Mac OS, and Linux and VNC into them, so I can test an application on multiple platforms? (with a paid subscription, of course)
If only DigitalOcean provided Windows and Mac Droplets it would be just what I'm looking for.
If none exists you can thank me for the idea :)

Browser testing on Windows 8?

I have a Mac and I am deciding whether to install Windows 7 or 8 on Boot Camp.
Is it possible to test websites inside actual windows of IE6+ and older Firefox/Chrome/Opera browsers with Windows 8?
I tried bootcamping a Core 2 Duo iMac a year or so ago with Windows 8 and it would cause regular crashes. It looks like there is an updated to Bootcamp (I was running the previous version 4) which supports Windows 8 so you could use either option.
If you use Windows 7 (like I did), you can install and run Windows Virtual PC with different versions of Windows and IE. The cool thing is Virtual PC has something called Integration Features which allows you to launch specific applications (like IE) from the virtual machines without being in the virtual machines. (Think virtual applications)
I do this. I have one Virtual PC with XP and IE6. I cloned it, upgraded it to IE7 and then did the same thing with IE8. Now I've got a Windows 7 machine with IE9 and virtual browsers of IE8, 7, and 6. I also run older versions of Firefox on those cloned XP machines.
If you use Windows 8 you can do the same thing, its just a little different procedure (see my comment below) because Windows 8 uses Hyper-V instead of Virtual PC. I prefer Virtual PC because of the Integration Features, with Windows 8 you'll have to use the Hyper-V console but you can do the same thing.
You'll need a virtual machine within Windows 8 to run anything earlier than IE10, since Windows 8 only started with IE10.
There are some hacks to make pages behave a bit "like" IE6 (or other browsers), but I doubt they are going to work well now you're reaching all the way back from IE10.
Firefox/Chrome/Opera will work OK, as they aren't integrated into the OS.
There are a couple of options that might work for you better than installing Windows 7 or 8 on bootcamp:
Use a service such as BrowserStack. This costs money, but Microsoft provides 3 free months via Modern.ie
Install virtual machines on your Mac. Microsoft makes these available for free, also via Modern.ie

ultimate virtual solution for testing <=IE8 browsers

I need to know of a solution to run a local test server through a virtual guest. I am able to use Virtual PC as well as most the other solutions. My current workaround is to deploy to Tomcat on Windows 7 and test the main current browsers there. I am also able to mount share my Tomcat instance to Ubuntu so am able to run the same app without redeploying.
Currently I just invested on a Windows upgrade to be able to try out Microsofts ie8 and down VHDs but the best I am able to do with this is deploy to production server and then run the ie6, ie7 and ie8 browsers which is very time consuming.
Any suggestions or pointers for me? Ultimately a working solution to run these VHds or browsers in VirtualBox would be ideal for me, as I am familiar with it.
Related to my question I have come across some useful tutorials that may help others who find this question:
Virtual PC solution for legacy IE browsers in Windows 7
VmWare solution
You can just use one Windows version (XP, Win7 will be fine) and install IETester:
http://www.my-debugbar.com/wiki/IETester/HomePage
My solution is as follows & will only work with upgraded Windows 7 (not home premium).
Uninstall IE9 update to bring back IE8, IE9 seems to support css3 well, so testing in FF7 should be good enough for IE9.
Then follow this tutorial and repeat the process for as many virtual browsers you want. Note
I did include IE8 but don't use it as it's slower to run a virtual PC than native IE8 just in case I wish to reinstall IE9.
I use quirks mode in IE8 to test for IE7 and IE6 can go to Davy Jones Locker :D
When using xpmode, you must copy the xp disk each time without any updates and start process from scratch.
I also use VirtualBox to test Linux browsers as it's faster than Virtual PC and I share test server (Tomcat) so am able to run same instance without redeploying.
Hope this helps...

What is your testing workflow for client-side web development on OS X?

What would be a good workflow on OS X for testing client-side code (HTML/JS/CSS) for browser compatibility and other issues across all major browsers?
I do my web development with Textmate (HTML and JavaScript), CSSEdit (CSS), and use Safari's Web Inspector, mainly for checking the JS console. I do have Parallels with Windows XP on it, but haven't tuned it for web development at all.
We develop on Macs too so what we usually do is testing and debugging in Firefox with the help of the Firebug plugin and the Web Developer toolbar. We then cross-check stuff in Chrome/Safari using Chrome's built-in Inspector in case of any discrepancies.
For testing on Windows we use a dedicated Windows machine that we can access through Remote Desktop which has some Virtual Machines running various versions of Internet Explorer (one VM for each would be nice, but we just use one for IE6, one for IE 7 and use the IE version that's installed on the remote machine as the third option).
A colleague of mine has a setup with VMWare and running IE right off his Macbook in a VirtualMachine.
As far as I can tell debugging in IE 6 is pretty hard, but some of the newer IE versions have a pretty decent Inspector similar to the ones in Safari and Chrome.