Its Strange I am back to square one again

Huh! I wished never to return back to the regression testing again, after my tryst with Alcatel project making stable regression and making test suites. But well history repeats. I am back to a similar profile job but with new technology of 4G. Learning is key here and I am definitely prepared to perform above expectations. I wish I have time from my debugging and troubleshooting to spend time on technology reads and doc preparations. I wonder why this document preparation is such an effort when u really wish to do it but time doesn't allow you to.

which is better !!

The data driven test framework or the test-driven test framework. Ofcourse I am in the middle of the the project. There is some framework code present and there is going to be development of new ones. Its not easy to decide which way to go - but Data driven surely looks much appeasing.
FYI,
Data Driven approach for test framework
Test driven approach for test framework

Any other suggestions are welcome!

An update!

My current book is Perl Cookbook - oreilly. Its such a nice book, good to refresh if you know the basics of Perl. Also have some exercises to do. I wish I knew about this book early to make me more confident for my interviews. But its never late. I am still starting on this book, covering the related chapters. But I do wish to read each and every page of the book for a nice understanding on how different modules/code can be more optimized. Nice book.

Test Framework

Lately i have been asked this question in my interview - how would you develop a test framework.

in my opinion the answer would be  - first we need to make a model/architecture/flow diagram on how is our testcase be executed . I have worked on a few architectures before - like table-driven and data-driven framework.
Whichever we choose, we should have a clear idea about what will be our input/from where do we choose our input from and it should be such that the code doesn't change when the input changes.
Next would be to develop the core functionality on how to test. We may follow some simple algorithms or more complex algorithms, but the epicenter should be it is simple to read and understand. It should be modular with no hardcoded values and properly documented. The more modular approach we take like packaging, global functions or include files, more better the code. Also having a layered architecture helps in later project lifecycle, as we need to change only a few modules when the project requirement changes.

While discussing the code functionality of the software development, we need to take care of how our outputs are been verified. Mostly verification of one or more functionality takes into consideration some of the analysis tools to be developed which again should be easy to use. These analyzers may be in-house or the third-party, but the APIs to be used via these analyzers should be comprehensive, flexible, understandable and easy to use. Providing more than one way of passing parameters to these modules helps in expanding our test framework at a later stage.

Lastly we should make sure, how our testcase output is being reported. A nicer approach would be to put all our testcase in some test suite and then posting the output on the XML output or on a web-page-based interface.

Aboveall, the environment setup to execute any test should be easy. We should consider writing smaller shell/perl scripts to set the environment rather than using basic linux/unix command line.

Bumped on this useful link

While preparing for my interview questions I bumped into this wonderful DB presented in form of a simple HTML page. http://kundansingh.com/interview/ . It may or may not have all the answers, but at least it can question you the basic of the interviews and to know if you really are prepared ?? 

cisco IOS Basic Config

line console 0 : global configuration that changes the context to console configuration mode.
line vty 1st-vty 2nd-vty : global config that changes the context to vty configuration mode for the range of vty lines listed in the command.
login : linke (console and vty) configuration mode. Tells IOS to prompt for a password (no usrname).
password pass-value : line (console and vty) config mode. Lists the password required if the login command(with no other params) is configured.
interface type port-number : global command that changes the context to interface mode - ex. interface Fastethernet 0/1.
shutdown/ no shutdown :Interface commands that enables/disables the interface.
hostname name : global command that sets this switches hostname which is also used as the first part of the switch;s command prompt.
enable secret pass-value : global command that sets the automatically encrypted enable secret password. The password is used for any user to reach enable mode.
enable password pass-value : global command that sets the clear text enable password, which is used only when the enable secret password is not configured.
exit : moves back to the next higher mode in configuration mode.
end : exits configuration mode and goes back to enable mode from any of the configuration submodes.
ctrl+z  : this is not a command, but rather a two-key combination that together do the same thing as the end command.
no debug all/ undebug all : enable mode EXEC command to disable all currently enabled debugs.
sow process : EXEC command that lists statistics about CPU utilization
terminal monitor : EXEC command that tells Cisco IOS to send a copy of all syslog messages, including debug messages, to the Telnet or SSH user who issues this command.
reload : enable mode EXEC command that reboots the switch or router.
copy from-location to-location : Enable mode EXEC command that copies files from one file location to another. Locations include the startup-config and running-config files, files on TFTP and RPC servers and flash memory.
copy running-config startup-config : Enable mode EXEC command that saves the active config, replacing the startup-config file used when the switch initialisex.
copy startup-config running-config : Enable mode EXEC command that merges the startup config file with the currently active config file in RAM.
show running-config : Lists the contents of the running-config file.
write erase/erase startup-config/erase nvram:   : All three enable mode EXEC commands erase the startup config file.
setup : Enable mode EXEC command that places the user in setup mode, in which Cisco IOS asks the user for input on simple switch configuration.
quit : EXEC command that disconnects the user from the CLI session
show system: running-config : same as show running-config command
show startup-config : lists the contents of the startup-config file.
show nvram:startup-config/ show nvram:   : same as show startup-config command.
enable : moves the user from user mode to enable(privileged)mode and prompts for an enable password if configured.
disable: moves the user from enable mode to user mode
configure terminal : enable mode command that moves the user into configuration command.

Important interview questions

Below are few important interview questions which should be answered thoughtfully and diplomatically.

1. If I were to get feedback from your manager, what would be the three things he would say.
2. What are your three week points or what are the three improvement areas would you like to work on.
3. Tell me something about yourself.
4. What were the projects you have been engaged in.
5. Tell me brief about any project you liked the most and why.

Few of the video questions!!

What is interlace scanning ?
What is progressive scanning ?
what is a pixel ?

What is HD and SD?

What is the maximum resolution in HD ?

more questions will follow !!!!!

Answers coming soon...