There are times when you are working on a remote linux or mac machine and you have to copy a file to your own *nix or mac machine. So, Tarun told me a way for that today. I am going to explain this with the help of an example. I am assuming that both the remote and the local machine are using mac OS
Suppose the IP of remote mac machine is 192.168.1.1 and the IP of your local machine is 192.168.1.2. The directory which you want to copy is located at /Users/remote/copyMe/ and the location where you want to place it on your machine is /Users/local/placeHere/ [sidenote: to find the IP of your machine. Run the Terminal and type ifconfig]
Now Open the Terminal on your local machine and type:
ssh [remote_ip_address] -l [remote_user_name]
i.e. ssh 192.168.1.1 -l root
Note here that it is small L (not one) switch after the remote address and that the remote_user_name is the username to access the remote machine
With this command you'll be asked for the login password. Once the correct password is filled you will be able to enter the remote machine. Now is the time to copy the directory [or just a file] from this remote machine to your local machine. This can be done in a single command. Like this:
scp -r [path to the source] [local_user_name]@[local_ip_address]:[path to the destination]
Now let me make it non-generic
scp -r /Users/remote/copyMe/ aman@192.168.1.2:/Users/local/placeHere/
Now all the contents of the remote directory 'copyMe', will be placed under 'placeHere' local directory. I have used a -r here to copy the directory recursively. if you are copying only a file then there is no need for this switch.
So was that so difficult! ;)
Thursday, June 5, 2008
Tuesday, April 29, 2008
How to use Older versions of Safari on Mac
For some testing purpose I needed Safari 2.0 on Mac OS X 10.4 [Tiger] as well as Mac OS X 10.5 [Leopard]. Few links which I felt are really helpful are:
http://michelf.com/projects/multi-safari/ - This link contains a number of old versions of Safari
http://tripledoubleyou.subtlegradient.com/stuff/Safari2/ - This link provides the method to install the Safari 2.0 on Mac 10.5 Leopard. I am just copying it down for backup purpose:
1. Download the zip — Safari 2.0.4.zip
2. Unzip the zip
3. Drag Safari 2.0.1 into your Applications folder
4. Wipe your LaunchServices cache by executing following command in Terminal:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
5. Enable the Debug Menu in your new Safari 2 by executing following command in Terminal:
defaults write com.apple.Safari.MultiSafari204 IncludeDebugMenu 1
6. Launch Safari 2.0.1
http://michelf.com/projects/multi-safari/ - This link contains a number of old versions of Safari
http://tripledoubleyou.subtlegradient.com/stuff/Safari2/ - This link provides the method to install the Safari 2.0 on Mac 10.5 Leopard. I am just copying it down for backup purpose:
1. Download the zip — Safari 2.0.4.zip
2. Unzip the zip
3. Drag Safari 2.0.1 into your Applications folder
4. Wipe your LaunchServices cache by executing following command in Terminal:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
5. Enable the Debug Menu in your new Safari 2 by executing following command in Terminal:
defaults write com.apple.Safari.MultiSafari204 IncludeDebugMenu 1
6. Launch Safari 2.0.1
Monday, April 28, 2008
Basic SQA Definitions
Very Strangely, I woke up early in the morning at around 6:15 AM. They say mind is fresh in the morning. My mind was so fresh, that I was having hard time deciding that what should I read? As I am a bit ill for few days, I was preferring not to look at the computer screen, so I decided to study something from a book. Moreover, I was reading Pressman's Testing book yester-night, so I decided to study the same chapter 'Testing Strategies'. Today I learnt the definitive difference between Unit, Integration, and Regression Testing. Actually, I am not a person who is good at definitions, but Tarn invoked me yesterday by asking some definitions related to SQA, so here is it now:
Unit Testing focuses verification effort on the smallest unit of software design - The software component or module. Unit Testing is usually adjunct to the coding step. Mostly, unit testing is done by the developer who is developing the software module. The developer uses drivers or stubs to input data (for data flow) to the module. Boundary testing is one of the most important part of the unit testing tasks.
Integration Testing is performed whenever a new module is added to an already (unit) tested module. The main purpose of the integration testing could be explained in one line as 'These two modules are working independently. Now test are they working correctly if we put them together. The integration testing could be performed in increments. It is known as incremental integration testing. I'll explain 'Incremental Integration Testing' in next post.
Regression Testing is re-executing some subset of tests that have already been conducted to ensure that changes have not propagated unintended side effects. Each time a new module is added as part of integration, the software changes, some new data paths are established and thus some problems may surface which are unattended. Regression Testing is done as a go-through-the-software process just to ensure that the changes have not propagated unattended side-effects.
A very good reference for those who are interested in Software Testing is http://amit-badola.blogspot.com/. This blog contains simple and precise explanations of the things related to SQA
Unit Testing focuses verification effort on the smallest unit of software design - The software component or module. Unit Testing is usually adjunct to the coding step. Mostly, unit testing is done by the developer who is developing the software module. The developer uses drivers or stubs to input data (for data flow) to the module. Boundary testing is one of the most important part of the unit testing tasks.
Integration Testing is performed whenever a new module is added to an already (unit) tested module. The main purpose of the integration testing could be explained in one line as 'These two modules are working independently. Now test are they working correctly if we put them together. The integration testing could be performed in increments. It is known as incremental integration testing. I'll explain 'Incremental Integration Testing' in next post.
Regression Testing is re-executing some subset of tests that have already been conducted to ensure that changes have not propagated unintended side effects. Each time a new module is added as part of integration, the software changes, some new data paths are established and thus some problems may surface which are unattended. Regression Testing is done as a go-through-the-software process just to ensure that the changes have not propagated unattended side-effects.
A very good reference for those who are interested in Software Testing is http://amit-badola.blogspot.com/. This blog contains simple and precise explanations of the things related to SQA
Validation vs. Verification
I spent a few hours on the book 'Software Engineering - A Practitioner's guide' by Roger S. Pressman. i was reading the chapter 'Testing Strategies', when I found some really interesting facts related to Validation and Verification. There is a strong divergence of opinion about what is 'validation' testing. Some people say that all testing is verification and the validation is conducted when the requirements are reviewed and approved, and when the system is operational, then user validates it. Other people believe that the unit and integration testing is verification and higher-order testing is validation. So overall-
Verication is Are we building the product Right?
Validation is Are we building the right product?
Verication is Are we building the product Right?
Validation is Are we building the right product?
The first mistake that people make is thinking that the testing team is responsible for assuring quality
Sunday, April 27, 2008
Why this blog?
I felt the need for this blog, as my mind does the monkey business when it comes to learning new technologies. One day I like to study android SDK, the other day I love coding for PHP-GTK and another day like studying databases. So this blog is to keep the track of the things which I learn.
Subscribe to:
Comments (Atom)