How To Make WiFi Tethering in Windows 10 or Windows 7?

It happens, specially when you are doing some testing with mobile devices, that you need to connect to only internally available application. The issue is with devices that have only WiFi connection and cannot be directly connected to internal network (LAN). For those cases you can create a temporary HotSpot (a connection sharing) on your Windows machine that will allow you to connect your device through it to your internal network, to have the following set-up:

Lets create the set-up:
Click Windows logo at the bottom left hand corner, type cmd, right-click the Cmd.exe link and select “Run as Administrator”. If you don’t have this option you cannot proceed. Sorry. Talk to your System Admin and show them this article.

But if you can the following black window will open up:

Here Type the command below:

netsh wlan set hostednetwork mode=allow ssid=MyNetwork key=MyPass

You of-course welcome to replace “MyNetwork” with the name you’d like to use for your new wifi network, and “MyPass” with a password of your choice.

NOTE: If after executing the command you get a command description response instead of the one you see in the image above, you probably have an issue with you password - it is to short - make it longer and things will look better.

While you are still at the command line, type

netsh wlan start hostednetwork

Now click Control Panel > Network and Internet > Network and Sharing Center > Change Adapter Settings.

In this window choose you regular LAN connection that you want to share. Right-click it and select Properties.

Click the Sharing tab, check “Allow other network users to connect…”, choose your virtual Wi-Fi adapter that will probably has a name of 'Wireless Network Connection 2'.

NOTE: The 'Wireless Network Connection' is probably your regular WiFi adapter and 'Wireless Network Connection 2' is the new virtual one that you have created in the commands before this is the one we want to share

Now on your Mobile device look for your “MyNetwork” WiFi network and use your “MyPass” as a password to connect.

Enjoy.....

Comments

Proper QA estimation in Agile project

Today, I want to chat about a common issue in Agile development – story point estimation. You see, it's easy to get caught up in estimating how long a feature will take to develop and forget about the crucial Quality Assurance (QA) effort. It happens to often: your team is in the middle of sprint planning. New user stories are being discussed, and estimations are given, but there's a catch. You've estimated the development time perfectly, but you've barely even glanced at how much effort QA will take. Why? Agile talks about Development Team and you mistakenly thought that it is all about DEVELOPMENT. Sound familiar? Trust me; it's a more common scenario than you might think. So, what's the big deal? Well, when you leave QA effort out of the equation, several not-so-great things can happen: Vilocity can suffer: You might think you can squeeze more into a sprint than is humanly possible, setting your team up for disappointment and overcommitment. Quality can de

Performance testing vs Load testing vs Stress testing

Today I want to discuss a popular topic regarding a difference between Load and Performance testing. Those two types of testing are commonly used together but there are several key differences between the two. To get a better understanding of the topic lets have a real life example from one of my clients and use it to explain the difference. I have worked for a client that was building an in-house web application that provides its customers with an option to select and order different products and services. The request was, before the up-coming release, to test the performance of their product. We started the task by trying and understand what they expect from performance point of view and then went through an exercise of defining what is captured by what test. The client said that they are looking to have about 900-1300 active users on the site at a given moment, and the expected response time (for a page to load) should be less than 5 seconds. With those details what are the t

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work. Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint. How we Calculate Velocity? Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be: 8+8+3=19 Note: the 32 story points are not part of the velocity calculation as this user story was not completed. What Velocity is used for? The v

QA Bean

Search This Blog