1)Creates file "myfile" filled with zeros with a block size of 1000 muliplied 10 tens or 10K
dd if=/dev/zero of=myfile bs=1024 count=10
2)Create 0 Byte file (or create batch file)
touch zero /touch 1 2 3 4 5
3)Create file with specify content
cat>>filename
one
two
^D (for exist)
Bug report management - configuration
Configuration for bug tracking system is very important.
Even you input the steps to reproduce the bugs...but need to make sure the other end actually do read them!!
Just found out the developers never got my 'steps to reproduce', since they never check in the 'advance options' in their profiles... or no one tell them to do ...
'Find'
find . -name smb.conf
Introduction
The Linux find command is very powerful. It can search the entire filesystem for one or more files that you specify. It's an extremely helpful Linux command to understand, especially when you need to find a file or directory.
Introduction
The Linux find command is very powerful. It can search the entire filesystem for one or more files that you specify. It's an extremely helpful Linux command to understand, especially when you need to find a file or directory.
cat /dev/null >
cat /dev/null >/path/file
In Unix-like operating systems, /dev/null or the null device is a special file that discards all data written to it
In Unix-like operating systems, /dev/null or the null device is a special file that discards all data written to it
Interview@Collins
No.1 Tell me about the two most important testing object?
No.2 When should testing be started?
No.2 When should testing be started?
We Love IE :P
Notes
(0012411)
ChengD (developer)
2009-11-18 09:41
cannot replicate the problem.
(0012412)
gracec (developer)
2009-11-18 10:28
On IE8 , Vista Platform.
(0012413)
ChengD (developer)
2009-11-18 10:39
JS Error.
I love IE.
Risk for testing #1
Internal structure is not working/stable.
Couldn't build the package for application, need to wait for fix, then publish the new build for testing
Couldn't build the package for application, need to wait for fix, then publish the new build for testing
Automation starting point
(10:15:21 AM) Marco: i'd start with part of system which is easiest to automate. reasons for this will be
(10:16:12 AM) Marco: you want to demonstrate to management that the time you spend on automation is goign to save time once u have it set up and running
(10:16:22 AM) Marco: to best prove automation has value
(10:16:36 AM) Marco: automate something easy. so that it will run reliably.
(10:17:06 AM) Marco: if you can get that to work..and convince some manager or developers you will have more support from them when or if the time comes to automate some harder parts of system
(10:17:07 AM) Grace: if they already decide to start automation anyway, is still the same ansers
(10:17:57 AM) Marco: yes i would still say same answer. the reason for this is i have gone into a several jobs where management was totally in support of automation, they had no clue, all they thought was we need to automate it will save us
(10:18:44 AM) Marco: n what happened was. when i explained that to setup automation it would take some time, or that developers might need to make changes to the src code to make it easier for automated test tools to hook into it..
(10:18:48 AM) Marco: thats when it started to fall apart
(10:18:56 AM) Grace: ah...
(10:19:24 AM) Marco: you want to avoid as much as possible the mentality by managers that 'automation will cure all our testing problems' without having to invest any time or effort in actually doing automation
(10:19:56 AM) Marco: so for these reasons based on my experience. start with somehting easy or small..
(10:20:06 AM) Marco: dont try to automate any parts of system that are unstable
(10:20:26 AM) Marco: if you can demonstrate that the tests run reliably 9 times out of 10
(10:20:28 AM) Marco: good
(10:21:16 AM) Marco: if u have tests that are running and failing for a bunch of reasons like network timeouts, or stuff that is outside your control then ppl will see that result. they will think. automation = waste of time
(10:22:19 AM) Marco: also my final comment. you won't convince everyone. but if you can convince even 1 or 2 of senior devs n someone in management and show them a good result from a small set of tests, you will have more support to automate the rest
(10:16:12 AM) Marco: you want to demonstrate to management that the time you spend on automation is goign to save time once u have it set up and running
(10:16:22 AM) Marco: to best prove automation has value
(10:16:36 AM) Marco: automate something easy. so that it will run reliably.
(10:17:06 AM) Marco: if you can get that to work..and convince some manager or developers you will have more support from them when or if the time comes to automate some harder parts of system
(10:17:07 AM) Grace: if they already decide to start automation anyway, is still the same ansers
(10:17:57 AM) Marco: yes i would still say same answer. the reason for this is i have gone into a several jobs where management was totally in support of automation, they had no clue, all they thought was we need to automate it will save us
(10:18:44 AM) Marco: n what happened was. when i explained that to setup automation it would take some time, or that developers might need to make changes to the src code to make it easier for automated test tools to hook into it..
(10:18:48 AM) Marco: thats when it started to fall apart
(10:18:56 AM) Grace: ah...
(10:19:24 AM) Marco: you want to avoid as much as possible the mentality by managers that 'automation will cure all our testing problems' without having to invest any time or effort in actually doing automation
(10:19:56 AM) Marco: so for these reasons based on my experience. start with somehting easy or small..
(10:20:06 AM) Marco: dont try to automate any parts of system that are unstable
(10:20:26 AM) Marco: if you can demonstrate that the tests run reliably 9 times out of 10
(10:20:28 AM) Marco: good
(10:21:16 AM) Marco: if u have tests that are running and failing for a bunch of reasons like network timeouts, or stuff that is outside your control then ppl will see that result. they will think. automation = waste of time
(10:22:19 AM) Marco: also my final comment. you won't convince everyone. but if you can convince even 1 or 2 of senior devs n someone in management and show them a good result from a small set of tests, you will have more support to automate the rest
Test Report
A bug report should including any outstanding risks or issues worth including, what we did well, what could be improved...
Except the test run result, defect result
Except the test run result, defect result
Connect MySQL via putty
cd /opt/xxxx/xxxx/mysql/bin/
./mysql -uroot -p ibahn_log -e "select * from Log" >result.txt
./mysql -uroot -p
show databases;
show tables;
./mysql -uroot -p ibahn_log -e "select * from Log" >result.txt
./mysql -uroot -p
show databases;
show tables;