]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
I’ve had a number of questions about the SET role and it seems I have confused folks when I say that the SWE is a tester and the SET is a tester and at the same time the SWE is a developer and the SET is a developer. What could possibly be confusing about that?
Oh, yeah. Right.
My next series of posts are going to detail the role of the SET and all will eventually be clear but some clarification on career path seems worthwhile.
SETs are developers who write test code and automation as their primary task. They are in every sense of the word a developer. When we interview SETs, SWEs are on the interview loop and SWE questions are asked. They are not all of the interview, but they are part of it.
This means that the skill set that our SETs possess makes them perfect candidates for switching to the SWE role. There is neither incentive nor deterrent to do so. SETs and SWEs are on the same pay scale and bonus structure (I have both roles reporting to me so I have real visibility into salary data) and their promotion velocity (again based on actual data) is roughly equivalent. This means that SETs have no outside influences to prompt them one way or the other.
The key factor is really the type of work you are doing. SETs who find themselves involved in SWE work usually convert to SWE. SWEs are also drawn in the opposite direction. Much of this happens through our 20% time work. Any SET interested in SWE work can take on a 20% task doing feature development. Any SWE interested in automation can find a group and sign up for a 20%. Right now I have both SWEs and SETs involved in such cross pollination.
The ideal situation is that the title reflects the actual work that you are involved in. So if an SET starts doing more feature dev work than automation, he or she should convert, same for SWEs doing automation work. In my time here, conversions in both directions have happened, but it is not all that common. The work of both roles is engaging, interesting and intense. Few Googlers are walking around bored.
Bottom line: do the work you are passionate about and capable of and the right job title will find you.
]]>
]]>
BJ Rolison (I.M.Testy) http://blogs.msdn.com/imtesty
BJ鏄井杞礋璐E宸ヤ綔鐨凾est Architecture錛屼篃鏄疕WTSaM鐨勪綔鑰呫備粬鐨勬枃绔犻潪甯告湁鏉＄悊錛岀湅璧鋒潵涔熸瘮杈冨鏄擄紝鍏朵腑鐨勬暟鎹篃闈炲父涓板瘜錛屾槸鎴戝枩嬈㈢殑椋庢牸銆?/span>
Alan Page http://blogs.msdn.com/alanpa/ Google Test Blog http://googletesting.blogspot.com Adam Goucher鐨勫崥瀹?nbsp; http://adam.goucher.ca/
Alan鏄井杞礋璐E宸ヤ綔鐨凞irector錛屾槸HWTSaM鐨勪富瑕佷綔鑰咃紝浠栫殑鍗氬鏄簡瑙ｅ井杞祴璇曢潪甯稿ソ鐨勪竴涓獥鍙ｃ傛渶榪戝嚑騫達紝浠栦笉闄愪簬嫻嬭瘯鎶鏈殑鎺ㄥ箍錛屼粬鏇村鐨勮冭檻鏄祴璇曠鐞嗭紝浠ュ強嫻嬭瘯姘涘洿/鏂囧寲鐨勫艦鎴愶紝浠ュ強瀵逛簬嫻嬭瘯鐨勫獎鍝嶃傛垜寰堝悓鎰忎粬鐨勪竴鍙ヨ瘽“95%鐨刄I鑷姩鍖栨祴璇曢兘鏄氮璐規椂闂?#8221;璇︽儏銆備粬鐨勫崥瀹㈡枃绔犳瘮杈冮殢鎰忥紝鏈夋椂涔熶笉鐭ラ亾浠栧湪鍞犲彣浜涗粈涔堬紝浣嗕笉鏃跺嵈鏈夊緢澶氱簿褰╃殑瑙傜偣銆?/span>
榪欐槸Google瀹樻柟鐨勬祴璇曞崥瀹紝淇℃伅閲忓緢灝戯紝闄や簡姣忓勾涓嬈＄殑Google Automation Test Conference涔嬪錛屾枃绔犺緝灝戙備粖騫?鏈堬紝James Whittaker紱誨紑寰蔣錛屽姞鍏oogle鍚庯紝鎵嶅埌榪欓噷澧炲姞涓嶅皯濂芥枃绔犮?/span>
James Bach鐨勫崥瀹?nbsp; http://www.satisfice.com/blog/
James鏄竴涓蔣浠舵祴璇曠殑璧勬繁浜哄＋錛?0騫翠唬鏇懼湪Apple鍜孊oland鍏徃錕斤拷錕借繃嫻嬭瘯綆＄悊宸ヤ綔錛屽悗鏉ュ湪鍏朵粬涓浜涘叕鍙歌礋璐ｆ祴璇曟祦紼嬪拰璐ㄩ噺綆＄悊錛?000騫磋嚜宸卞垱鍔炰簡satisfice嫻嬭瘯鍜ㄨ鍏徃錛屾彁渚涜蔣浠惰川閲忎繚璇佺浉鍏崇殑鍜ㄨ鍜屽煿璁? 浠栧拰Cem Kaner鎾板啓浜嗗緢澶欵xplorary Testing鐩稿叧鐨勬枃绔犲拰涔︾睄錛屽茍涓旀彁鍑轟簡Context-Driven-Testing錛岃繖浜涙柟娉曡寰堥傚悎鐜板湪鐨凙gile Testing鐨勭壒鐐廣?/span>
涓涓浜ч珮璐ㄧ殑嫻嬭瘯鍐欎綔涓撳錛屽熀鏈笂姣忎釜鏈堥兘鏈?0澶氱瘒鍏充簬嫻嬭瘯鐨勬枃绔狅紝鏈夋椂鍊欎竴澶╁啓浜嗗綃囷紝鐪熸槸闈炲父浣╂湇浠栫殑鍐欎綔鑳藉姏銆備粬鐨勬濇兂寰堟湁娣卞害錛屽杞歡嫻嬭瘯鍚勪釜鏂歸潰閮芥湁鍏ㄩ潰鐨勭悊瑙ｏ紝浠栭槄璇諱簡鍑犱箮鎵鏈夋柊鍑虹殑嫻嬭瘯涔︾睄錛屽茍涓斾簺浜嗕笌鍏剁浉鍏崇殑璇勮銆傝繖浜涜瘎璁洪氬父闈炲父灝栭攼銆傛瘮濡傝錛?a title="Shift + Click to follow link" mce_>HWTSaM鐨勮瘎璁?/a>,浠栫殑璇勮灝辨瘮杈冧腑鑲傚James Whittalkes鐨?Exploratory Testing璇勮 鍗存槸鍡や箣浠ラ薊銆?/span>
杞歡嫻嬭瘯鏉傛枃闆嗭細http://blogs.msdn.com/b/cheno/
鏂囩珷杞嚜錛?a >http://www.cesoo.com/