Tuesday, September 16, 2008
Bumptop Beta Testing Feedback:
Sunday, September 14, 2008
Chrome_Crash_Event_ID_Information:
For security reasons.
I have to hide the computer name.
Data in Bytes:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 63 68 72 6f 6d 65 chrome
0018: 2e 65 78 65 20 30 2e 30 .exe 0.0
0020: 2e 30 2e 30 20 69 6e 20 .0.0 in
0028: 68 75 6e 67 61 70 70 20 hungapp
0030: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0038: 61 74 20 6f 66 66 73 65 at offse
0040: 74 20 30 30 30 30 30 30 t 000000
0048: 30 30 00
Wednesday, September 03, 2008
Google Chrome
Sunday, August 31, 2008
More about SCRUM:
Scrum is really a project management methodology to facilitate agile software development, and enable the creation of self-organizing agile teams. A ScrumMaster is like a traditional project manager in the sense that he/she oversees the centralization of team communication, requirements, schedules and progress.
But it is also very different because his/her main responsibility is to facilitate team communications and provide guidance and coaching, while removing impediments to the ability of the team to deliver its goals. Unlike a traditional project manager, the ScrumMaster doesn’t direct the team, because an agile team is based on the philosophy that a team member is committed to the other team members, not to a management authority.
Tuesday, July 29, 2008
Test closure activities :
During test closure activities, we collect data from completed test activities to consolidate experience, including checking and filing testware, and analyzing facts and numbers. We may need to do this when software is delivered. We also might close testing for other reasons, such as when we have gathered the infor-mation needed from testing, when the project is cancelled, when a particular milestone is achieved, or when a maintenance release or update is done.
Test closure activities include the following major tasks:
1.) Check which planned deliverables we actually delivered and ensure all incident reports have been resolved through defect repair or deferral.
2.) Finalize and archive testware, such as scripts, the test environment, and any other test infrastructure, for later reuse.
3.) Hand over testware to the maintenance organization who will support the software and make any bug fixes or maintenance changes, for use in con firmation testing and regression testing.
4.) Evaluate how the testing went and analyze lessons learned for future releases and projects.
-
Although the title UI Designer suggests a sort of departure from the traditional graphic designer , UI design is still a part of the hi...
-
MonkeyRunner Automation Testing Tool for Android O.S: The monkeyrunner tool provides an API for writing programs that control an Android de...
-
UhuruAppCloud Service: (Exploration Testing) It's a new cloud based application hosting service. Nice and fast UI, I can ...
The USB-C Moment for AI: A Student’s Guide to the Model Context Protocol (MCP)
The USB-C Moment for AI: A Student’s Guide to the Model Context Protocol (MCP) In the rapidly evolving world of Artificial Intelligence, ...