x - delete current character
dw - delete current word
dd - delete current line
5dd - delete five lines
d$ - delete to end of line
d0 - delete to beginning of line
:1,.d
delete to beginning of file
:.,$d
delete to end of file
Marcus French
Job Title:
Engineer
Contact:
Marcus - Developer with experience designing and developing desktop and web applications using Java, Ruby on Rails, and PHP, and public-facing websites using PHP content management systems (Drupal, Magento, Joomla, WordPress). Experience with Oracle, SQLServer, and MySQL databases. Experience with SVN, Bzr. Extensive experience with Excel, including Macro/VB development.
- Software Quality Assurance Engineer with experience leading QA teams in the planning, designing, execution, and reporting of automated performance and functional tests for desktop and web applications using LoadRunner, Quick Test Professional, Quality Center, Performance Center, FitNesse, Selenium, AppLoader, and Grinder. Experience upgrading and operating QA software for large organizations (PC and QC).
- Extensive experience designing processes, handling communication/meetings, and managing resources to ensure software defects are brought through to resolution utilizing Quality Center.
Resume:
My Blog
Thu, 01/26/2012 - 18:22
Tue, 01/10/2012 - 20:10
1. yum install unixODBC freetds freetds-devel unixODBC-devel
2. Add your database to /etc/freetds.conf:
[(your custom connection name)]
host = (your host)
port = 1433
tds version = 7.0
username = (username)
password = (password)
3. Add this to /etc/odbcinst.ini:
[FreeTDS]
Description = TDS driver (Sybase/MS SQL)
Driver = /usr/lib64/libtdsodbc.so
Setup = /usr/lib64/libtdsS.so
CPTimeout =
CPReuse =
FileUsage = 1
4. Add your database to /etc/odb.ini:
[(your custom connection name)]
Driver = FreeTDS
Description = ODBC connection via FreeTDS
Trace = No
Servername = (your custom connection name)
Database = (your db name)
5. Install the following gems:
- 'dbi'
- 'ruby-odbc'
- 'dbd-odbc'
6. Connect using something like:
require 'dbi'
@connection = DBI.connect("DBI:ODBC:(your custom connection name)", (username), (password))
Mon, 01/09/2012 - 00:08
Basic Flow of a Performance Test, as I've done them, for those interested:
1) Use The Grinder's TCPProxy to record a series of user stories, making sure to put in comments as you record
2) Trim down the scripts to only issue the necessary commands, delete the sleep times
3) Put in some text handling and error checking into the scripts to make things like searches into variable-based scripts, and custom site error responses (such as login redirects) into Grinder errors
4) Create a main script to handle all the different scripts, varying the scripts that are running based on thread number and random numbers to create the vUser distribution required
5) Create a grinder.properties file that runs the test in question (baseline, stress, etc...)
6) Run nmon or perfmon on the web server, app server, db server, etc...
7) Start the test using the Grinder Console
8) Stop the test and gather the results
9) Use CSVSee and the grinder output format to create the transaction statistics
10) Use a stat analyzer such as nmon analyzer to create meaningful statistics
11) Gather the statistics and create a summary report outlining the test, the gathered statistics, analysis, and predictions based on the test