Tag Archive: computers


Absolutely stunning. The Sixth sense technology.
Guys – must watch!!

Absolutely stunning to see where technology is heading and what the future is gonna look like.

And be proud – the man behind this is an Indian!!

This is just incredible and unbelievable, yet true. Click the URL below and see the demo and find out how things are going to change in the computer world.

See the live demo of Pranav Mistry who shook the world recently on this Sixth Sense Technology.

This is simply a terrific presentation and absolutely astounding!! !!!!

At TED India, Pranav Mistry demos several tools that help the physical world interact with the world of data — including a deep look at his SixthSense device and a new, paradigm-shifting paper “laptop”.

In an onstage Q&A, Mistry says he’ll open-source the software behind Sixth Sense, to open its possibilities to all. MICROSOFT better watch out.

http://economictimes.indiatimes.com/Pranav-Mistry-The-thrilling-potential-of-SixthSense-technology/videoshow_ted/5231080.cms

Advertisements

We can print one document in Windows XP.
But how to we print all files in the folders? Ok.
If one folder has 10 files we can open all files and then give print command. If 100 files are there and you have to take a printout of all of them what can we do? Here only notepad comes to our help here we can write a batch file and command it to print from a right place. Lets see briefly how is this done.

First of all open note pad, through Start, All Programs, Accessories, Notepad then type the following code without fault.

@echo off

dir%1/-p/o: gin>

“%temp%listing”

Start/wnotepad/p”%temp%listing”

Del”%temp%%listing”

exit

Save the file as printdir.bat, then save it in c:windows folder. A small tip: – you can save this file in any name but you must give the extension as .bat only. Now you have successfully created a file to print. Now, let’s see how to print all files in a folder,

1) First double click the My Computer icon.
2) Select Folder options from the Tools menu
3) Then Click File types tab, it will be in the upper side of the screen.
4) You will find a file type below” Registered file types”
5) Select it and click Advanced Tab
6) This opens Edit File Type. In this you can see a button “New” click it
7) New action dialog box opens
8)Type print directory in action tab
9) Browse for c:windowsprintdir.bat through browse button at application used to perform action
10) Click ok and close all the dialog boxes

If lot of files is to be printed we can create a folder and put them inside it, now right click on the folder and select print directory option in it, if you select this all files in the folder will be printed.

Care should be taken when communicating fault information to developers and managers. In ancient Greece messengers who brought bad news were executed so some things have improved! 🙂 However, we must still tread carefully.

Dashing up to a developer and saying “You fool, you did this wrong” is not likely to encourage him or her to investigate the problem. More likely the developer will go on the defensive, perhaps arguing that it is not a fault but it is the tester who does not understand it.

A more successful approach may be to approach the developer saying “I don’t understand this, would you mind explaining it to me please?” In demonstrating it to the tester the developer may then spot the fault and offer to fix it there and then.

Cem Kaner (co-author of “Testing Computer Software”) says that the best tester is not the one who finds the most faults but the one who manages to have the most faults fixed. This requires a good relationship with developers.

So from next time when you are raising a defect please follow the above given approach and you’ll c the diference it makes.

An Indian-origin scientist in the US has claimed that with processing speeds getting faster, laptops may soon get as hot as sun.
   “Laptops are very hot now, so hot that they are not ‘lap’ tops anymore,” said Avik Ghosh, assistant professor at the University of Virginia School of Engineering and Applied Science. “The prediction is that if we continue at our current pace of miniaturisation, these devices will be as hot as the sun in 10 to 20 years.”
   Researchers at the University are working to overcome the excess heat generating problem using nanoelectronics, expected to power the next generation of computers.
   Ghosh and Mircea Stan, also a professor in the department, are re-examining nothing less than the Second Law of Thermodynamics. The law states that, left to itself, heat will transfer from a hotter unit to a cooler one — in this case between electrical computer components — until both have roughly the same temperature, a state called “thermal equilibrium.”
   The possibility of breaking the law will require Ghosh and Stan to solve a scientifically controversial — and theoretical — conundrum known as “Maxwell’s Demon.”
   Introduced by Scottish physicist James Clerk Maxwell in 1871, the concept theorises that the energy flow from hot to cold could be disrupted if there were a way to control the transfer of energy between two units. Maxwell’s Demon would allow one component to take the heat while the other worked at a lower temperature.
   This could be accomplished only if the degree of natural disorder, or entropy, were reduced. And that’s the “demon” in Maxwell’s Demon. “Device engineering is typically based on operating near thermal equilibrium,” Ghosh said. But, he added, nature has examples of biological cells that operate outside thermal equilibrium. Chlorophyll, for example, can convert photons into energy in highly efficient ways that seem to violate traditional thermodynamic expectations,” .

Hi Here comes some details wrt what types of testing one can perform.
I hope you’ll find the list useful.

  • Black box testing – not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
  • White box testing – based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.
  • unit testing – the most ‘micro’ scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
  • incremental integration testing – continuous testing of an application as new functionality is added; requires that various aspects of an application’s functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
  • integration testing – testing of combined parts of an application to determine if they function together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
  • functional testing – black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (which of course applies to any stage of testing.)
  • system testing – black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
  • end-to-end testing – similar to system testing; the ‘macro’ end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
  • sanity testing or smoke testing – typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a ‘sane’ enough condition to warrant further testing in its current state.
  • regression testing – re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.
  • acceptance testing – final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
  • load testing – testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
  • stress testing – term often used interchangeably with ‘load’ and ‘performance’ testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
  • performance testing – term often used interchangeably with ‘stress’ and ‘load’ testing. Ideally ‘performance’ testing (and any other ‘type’ of testing) is defined in requirements documentation or QA or Test Plans.
  • usability testing – testing for ‘user-friendliness’. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
  • install/uninstall testing – testing of full, partial, or upgrade install/uninstall processes.
  • recovery testing – testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
  • failover testing – typically used interchangeably with ‘recovery testing’
  • security testing – testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
  • compatability testing – testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
  • exploratory testing – often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
  • ad-hoc testing – similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
  • context-driven testing – testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.
  • user acceptance testing – determining if software is satisfactory to an end-user or customer.
  • comparison testing – comparing software weaknesses and strengths to competing products.
  • alpha testing – testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
  • beta testing – testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
  • mutation testing – a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes (‘bugs’) and retesting with the original test data/cases to determine if the ‘bugs’ are detected. Proper implementation requires large computational resources.