Category → Testing
Test Engineering Goals
- Architect test automation framework for rapid and efficient test automation development
- Scale test model
- Automated E2E and Scale Test
Managed Code Performance
Yesterday, I spent 2 hours to rewrite one parser code that my report wrote. The goal was to see if the parser could perform better while the code looks more organized and simpler to follow. For every text process, I tend to use the regular expression because of the simplicity and cleanness it provides, but I was not 100% sure if it could overcome the performance issue as Managed Code is known to be slow in many aspects.
The first attempt was disaster as it took probably 2 or 3 times more to process the same amount of data. While I was reading the code again before I gave up, I realized one mistake and one thing that I forgot. Regular expression in .NET is slow by default during run-time unless a specific option is specified during initialization – RegexOptions.Compiled.
http://msdn.microsoft.com/en-us/library/system.text.regularexpressions.regexoptions.aspx
Also here is a good MSDN article about the improving the performance of the base library.
Best SDET Candidates
For the past one year I have interviewed enough people to set my own standard for the best SDET candidates. Here is the list of credentials that I am looking for when I interview SDET:
- Coding skill – This is a must. What I don’t want to see is using a data structure without a good reason. That explains the level of understanding of software engineering.
- Tester eyes – Can you catch critical flow of your code? Can you catch edge cases of a program?
- Scope – Can you generalize a problem? Can you extend the idea beyond a problem asked?
- Communication skill – Do you ask if a problem is not clear? Can you negotiate with a good reason?
TOREAD
- Agile Project Management with Scrum
- Automated Defect Prevention: Best Practices in Software Management
- Software Estimation: Demystifying the Black Art
Five Orders of Ignorance
The Five Orders of Ignorance – Philip G. Armour
- 0th Order Ignorance (0OI)—Lack of Ignorance.
You know the question and you even know the answer. - 1st Order Ignorance (1OI)—Lack of Knowledge.
You don’t know the answer, but you at least know the question. - 2nd Order Ignorance (2OI)—Lack of Awareness.
You don’t know the answer or the question, but you know you don’t know and you have a way to find it. - 3rd Order Ignorance (3OI)—Lack of Process.
You have no way to discover that you are unaware of your ignorance. - 4th Order Ignorance (4OI)—Meta Ignorance.
You don’t know that there are Five Orders of Ignorance; now you do.
What is your order of ignorance?
Recent Comments