Gadget

目前仍無法透過加密連線存取這項內容。

Categories

工作態度 (1)    方法論 (5)    本土化 (9)    危機管理 (2)    死亡 (1)    自我成長 (1)    自我管理 (3)    決策管理 (1)    版本 (1)    社會 (2)    品管 (3)    風險管理 (1)    效能 問題 (1)    時間管理 (5)    專案 (10)    教育 (1)    產能 (1)    產業 (5)    軟體 (4)    測試 (10)    閒聊 (14)    溝通 (4)    道德 (1)    漫談 (23)    管理 (1)    機器翻譯 (1)    簡轉繁 (2)    翻譯 (8)    booksore (1)    Chinese (1)    Flash (1)    G11N (1)    I18N (3)    Industry (1)    L10N (8)    politics (1)    Project Management (6)    Revision (1)    Software (3)    Testing (4)    Time Management (1)    Translation (4)    UI Design (1)   

2005年7月12日

責任與承諾

什麼叫做承諾?什麼叫做責任?承諾與責任,又是怎樣的關係?

邁向下一個階段

終於要離開現在的公司了。數一數日子,也超過三年的光陰了。比起第一份工作,待了將近四年,第二份工作超過三年,加起來正好七年。

第一份工作雖是在學術單位,好歹也是個組長,帶了個小組做些技術開發與維護。第二份工作被當作正式踏入社會,新的工作領域,想說就多學學吧,先是個工程師,也幹了兩年,邁入第三年才升資深工程師。工作資歷不能拿年紀來比,要拿實際的工作年資來比。沒服兵役也沒念研究所,大學畢業後直接工作,這樣比起一些有念研究所又有服兵役的人來說,工作資歷馬上多了四年。雖然念研究所的,在一些公司裡的職等是會跟大學畢業的有所區隔啦。

現在堂堂邁入第八個工作年頭,還是一屆資深工程師。

我想,假設有人試著要了解我為什麼要離開工程師,他可能要問很多人,也才能拼湊出約略50%。當然問我是最快的,可是基本上人都是看對方是什麼人,才決定對他說些什麼。總是有親疏遠近,總是有職務上的直接間接相關。

其實,人家說,要想留住優秀員工,不是等到他提了離職,才開始想辦法留住他。這麼說,姑且說我是優秀員工吧,我待了三年,之前都沒走,或許可以說是公司的一些相關福利、制度、升遷等等之類的,沒讓我想走。那麼現在想走了,是不是算是對現狀不滿呢?還是說我不算是優秀員工?

無論如何,有不少事情自己心裡其實很清楚,時機時機吧,每個人有每個人在不同時期所適合的不同的職場。比如在第一份工作裡,那裡的職場很能讓我好好發揮,一來工作內容跟自己專長有相關,也有興趣,二來當時的架構來看由我帶領一個技術團隊也很適合。

人或許該要盡量忘卻過去的不愉快不歡喜,少講些過往的閒言閒語,多看看未來,多規劃以後的路,是吧!

下一個階段是怎樣呢?

2005年7月11日

中平籤詩一首

事端百出慮雖長
莫聽人言自主張
一著先機君記取
紛紛鬧裡更思量

What kinds of testing should be considered?






















































































































Type of Testing Description
Black box testing Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
Incremental integration testing
Continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

Integration testing

Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing

Black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

System testing

Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.

End-to-end testing

similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity testing or smoke testing

Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

Smoke tests get their name from the electronics industry. The circuits are laid out on a bread board and power is applied. If anything starts smoking, there is a problem. In the software industry, smoke testing is a shallow and wide approach to the application. You test all areas of the application without getting too deep. This is also known as a Build Verification test or BVT.

Regression testing

Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

Acceptance testing

Final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.

Load testing

Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.

Stress testing

Term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

Performance testing

Term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

Usability testing

Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

Install/uninstall testing

Testing of full, partial, or upgrade install/uninstall processes.

Recovery testing

Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Failover testing

typically used interchangeably with 'recovery testing'

Security testing

Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.

Compatibility testing

Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.

Exploratory testing

Often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.

Ad-hoc testing

Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.

Context-driven testing

Testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.

User acceptance testing

Determining if software is satisfactory to an end-user or customer.

Comparison testing

Comparing software weaknesses and strengths to competing products.

Alpha testing

Testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Beta testing

Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

Mutation testing

a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.