Play as Webslides

mikeem em's List: Work_software_testing

Software Testing tips: Automation White Papers

tips-testing.blogspot.com/...automation-white-papers.html - Preview

testing on 2009-11-25
Why China Has to Steal Technology

hnn.us/11405.html - Preview

china current_affairs on 2008-11-09
YouTube - Propellerhead Reason Tutorial - Making A Bass Line

www.youtube.com/watch - Preview

music_production propellerhead reason video tutorial on 2008-10-25
Testing abbreviations | testingReflections.com

www.testingreflections.com/...2194 - Preview

testing abbreviations dictionary on 2008-10-22
Test & QA Report - SD Times On The Web

reports on aspects of testing. overall, site is very good

www.sdtimes.com/...tqareport.aspx - Preview

reports testing sd timestesting blog articles on 2009-01-11
Software Testing | uTest Software Testing Forum

www.utest.com/3 - Preview

test forum advice testing on 2008-10-17
Website Critiques Forums

forums.devshed.com/website-critiques-89 - Preview

work website site design on 2008-10-17 and saved by 2 people
What does a software tester do? - Dev Shed

forums.devshed.com/...software-tester-do-328623.html - Preview

software tester commentsilike on 2008-10-16
- I would have thought the title of "Software Tester" was self explanitory. A "Software Tester", tests software.
  
  ...and no, being a "Software Tester" would not require you to have software development skills. Those are skills required (oddly enough) by a "Software Developer".
  
  sheesh.
DevelopSense Blog: 07/01/2007 - 08/01/2007

blog of one tester. good to read occasionaly

www.developsense.com/...2007_07_01_archive.html - Preview

testing blog on 2008-10-16
Thinking Tester: Dr. Cem Kaner on Software Testing as a Career

advice on software development as a career choice . good

shrinik.blogspot.com/...er-on-software-testing-as.html - Preview

testing career advice good on 2008-10-16
- I don't generally encourage my students to pursue software testing AS A CAREER. They can make that decision later, after they have more experience. I prefer to encourage them to try SOFTWARE DEVELOPMENT as a career -- to me, development includes testing. And that they take a job doing serious, skilled testing as PART of that career. Most of the best testers I know have significant experience outside of testing and apply that experience to what they do as testers or test managers.
- I don't recommend that people make a decision to narrow their career that much, early in their career. Let them explore the field more, in their next few jobs, before they lock themselves into something.
- 2 more annotations...
- - constantly learn new things, about the product, its market, its implementation, its risks, its usability, etc. To learn these, we are constantly developing new skills and new cognitive structures in a diversity of fields
  - Learning to do good software testing requires learning to do critical thinking well, and to back it up with empirical research. Not everyone will like to do testing. Not every engineer or programmer will have the skills or the interest to do professional-level testing. But for those of us who enjoy critical thinking, experimentation, and keeping the human relevance of what we do always in mind, there is nothing else like it in software development (except, for some people on some projects, requirements analysis backed with rapid prototyping and prototype-based research).
Lost in translation - SD Times On The Web

Requirements and specs - the difference

www.sdtimes.com/...32967 - Preview

requirements specs testing on 2008-10-16
- Requirements “define necessary objectives” on the part of the end user, according to technical essayist Derek Sisson. Requirements let everyone know what the program is supposed to do—critical information for developers and testers.
- “a requirement is an objective that must be met
- 19 more annotations...
- - requirements world is a fluid, somewhat fuzzy space where users know what they want but struggle to express it clearly enough for developers and testers to produce applications that meet the users' needs
  - rigidly structured world of specifications, whose inhabitants converse in tech speak, execute tasks in narrowly defined ways and deal in specialized knowledge that outsiders find difficult to grasp.
    
    “Specifications provide formalization and detail around a specific requirement,” observed Bola Rotibi, an analyst with MWD Advisors. But important details can be lost in translation from the customer’s concept to the developer’s spec.
  - Because the customer doesn’t know all the technical aspects of creating an application that meets the need, requirements are often “too loose and vague,”
  - “Even among native English speakers, different people can interpret the same set of words in different ways. Expand this to a global scope of international English, and the problems are worse.”
  - Users sometimes neglect to tell developers about “nonfunctional requirements,”
  - An example is “performance at peak usage times; people forget to state this up front. Then development goes down a path not knowing a key need: The app must scale for thousands of users.”
  - “I suspect this problem exists for a variety of reasons, but one leading cause may be that many companies overload developers and testers with the added responsibility—and burden—of pretending to understand the customer’s needs as well as the marketing people or program managers [do].
  - “To paraphrase Bill Gates, it is important for testers and developers to have exposure to customers, but it should be different from the program manager’s exposure.”
  - Users get frustrated because their requirements are not being met, or the requirements they communicated really aren’t the requirements, or the act of meeting the requirements produced unexpected and unpleasant side effects. User dissatisfaction in turn lengthens the development cycle and raises costs, since developers have to write and rewrite code, and testers have to scrap test specifications and start from scratch to comply with a moving target.
  - It takes open communication, sharing of information and plain old accountability. “If a customer says, ‘I would like to do X,’ that’s fine, as long as they are aware of the potential risks and what needs to be in place,”
  - “Relying on developers to design a software program would be similar to relying on an engine mechanic to design a car,” Rollison said. “Engine mechanics could probably design a car with some really cool bells and whistles, but the only truly satisfied customers would be other engine mechanics.”
  - Testers shouldn’t be expected to identify design problems after implementation, either. “Too costly,”
  - “Create a project charter that outlines everyone’s roles and responsibilities. Pay close attention to scope and scope creep. Yes, you will obtain new ideas, features and functions along the way, but capture them for version 2.0. Don't let your project grow on its own.”
  - Agile’s manifesto states that it values responding to change over following a plan, and that developers should welcome changing requirements, even late in the development cycle. Agile development counts on iterative production that delivers working software frequently.
  - “If you design a system so rigid that you have to get it right the first time, it’s guaranteed to fail. Developers would much rather the requirements be well defined and not change. It would make life so much easier. But that’s just not the reality.
  - The best way to act is incrementally, meaning that you design bits; you don’t design a huge system. You plan to go back and revise the things you’ve designed, in an agile way, to reduce the penalty of being wrong.
  - What we need to do is simulate, as early as possible, the software experience for the users.”
  - “For example, one can quickly simulate the software experience by capturing a definition of user profiles, constructing user-perspective use cases, constructing paper-and-pencil-based prototypes of those use cases, and presenting a storyboard animation of those use cases to let users quickly see what the software would look like and feel like.
  - Yooplus’ Christel echoed Eshelby’s sentiment on teamwork. “Include your customer in the entire process, including requirements gathering, focus groups and beta testing. Include your IT project manager. Create an open collaboration, with project transparency.”
Special Reports - SD Times On The Web

good info on the software industry ect.

www.sdtimes.com/...specialreport.aspx - Preview

software mag on 2008-10-16
'Testers Are Idiots' Revisited - SD Times On The Web

www.sdtimes.com/...32961 - Preview

testing article on 2008-10-16
- testers and developers should receive equal pay, have comparable career paths and equal say with other company organizations about product decisions
- “Maybe not as far as the ship/don’t ship decisions, but they should have a say in strategy and product decisions. When I was a tester in a small shop, everything [that went wrong] was my fault,” Feldstein said.
- 1 more annotations...
- - test organizations need to focus more on customer advocacy and less on becoming a police state. “It could be as simple as changing the department name from QA or testing department to the product validation or product verification department,” she said. While such a change might seem superficial and simplistic, she continued, the perception of the department’s function over time will “slowly change to one of core business value.”
Software Testing and Quality Assurance Online Forums

www.qaforums.com - Preview

testing forum on 2008-10-16 and saved by 15 people
Static Testing

www.onestoptesting.com/...introduction.asp - Preview

static testing on 2008-10-16
- Static testing is a form of software testing where the software isn't
  actually used. This is in contrast to Dynamic testing. It is generally not
  detailed testing, but checks mainly for the sanity of the code, algorithm, or
  document.
Static Testing

good source of testing info

www.onestoptesting.com/static-testing - Preview

test forum on 2008-10-16
ronpih's weblog : Software Testing Blogs

list of testing blogs

blogs.msdn.com/...software-testing-blogs.aspx - Preview

software testing on 2008-10-16

1 - 17 of 17

Showing 20▼ items per page

List Comments (0)

List Info

mikeem em

17 items | 17 visits

Updated on 2009-11-25
Created on 2008-10-16

Category: Business & Finance

business software testing

URL:

mikeem em's List: Work_software_testing

Software Testing tips: Automation White Papers

Why China Has to Steal Technology

YouTube - Propellerhead Reason Tutorial - Making A Bass Line

Testing abbreviations | testingReflections.com

Test & QA Report - SD Times On The Web

Software Testing | uTest Software Testing Forum

Website Critiques Forums

What does a software tester do? - Dev Shed

DevelopSense Blog: 07/01/2007 - 08/01/2007

Thinking Tester: Dr. Cem Kaner on Software Testing as a Career

Lost in translation - SD Times On The Web

Special Reports - SD Times On The Web

'Testers Are Idiots' Revisited - SD Times On The Web

Software Testing and Quality Assurance Online Forums

Static Testing

Static Testing

ronpih's weblog : Software Testing Blogs

List Info

Sponsored Links

mikeem em's Public Lists (14)