The false positive refers to a software behavior that does not seem correct at first glance, but, once you analyze what you’ve done, you begin to realize that the software behavior is correct, and you made a logical mistake somewhere along the way.
How frequently do you run into situation?
1. This depends on a user experience level of a QA team who finds the bug.
2. People who do not have a time and patience to analyze the bug run into this quiet often.
3. This is usually the case when dealing with complex or totally new part of software…
I worked in software quality assurance using waterfall method for quite a long 19 years.
I have never worked in a Scrum environment.
I now am seeing many job postings referring to agile scrum approach with 2-week sprint releases.
As far as I know, the scrum is a software development approach designed to release new software changes on a regular basis compared to a waterfall approach with less frequency.
The Scrum master decides what to include in a two-week sprint release. The scrum master holds daily progress meetings with status updates.
The two-weeks is now standard in most scrum teams.
T / Tech job postings require way too many IT technologies and skills.
The range of Udemy course topics satisfies most job requirements.
Therefore, a person changing careers should take several Udemy courses for a particular IT/Tech role.
I like Udemy for the following reasons:
1) The range of courses on a particular topic
2) For each course, before buying the course, I can see the depth of material covered for each topic.
3) Some courses have quizzes and coding assignments in each section of a course which requires a student to understand the material and spend the time mastering…
Software test engineer grows from junior to senior learning the software programs necessary to do the job, gaining domain knowledge, and becoming proficient in the core skills.
I) The software programs
II) Domain knowledge
1) For some software products, software test engineer needs to gain domain knowledge.
2) The domain knowledge requires an understanding of the specific terminology and the core theory.
3) Domain knowledge adds a lot of value in communication:
with users outside the software development team, reviewing the software requirements document, reading and responding to emails, reviewing bug tickets, and communicating test results.
4) Examples of domain…
In some software products, adding a new user depends on the user role.
The user role is the level of responsibility within(internal user) or outside(external user) the company.
The level of responsibility determines the user rights within the software program.
A software user with higher responsibility has more rights and vise versa.
The user rights refer to allowed user actions in the software program.
The following examples with three users illustrate the user roles and rights concept:
The supervisor user can:
a) add, remove, or change rights for internal and external users. …
Test Results report is a detailed summary of all tests performed for a particular testing project.
The testing project could be:
a) New enhancement or new changes testing
b) Bug testing
c) A testing project with a specific focus
The test results report is the standard requirement in the software testing process enforced by Software auditing companies.
The software test engineer writes the test results report upon the successful completion of all software tests executed. The software ticket must include the test results report in the bug management program.
The test results report includes:
a) The summary of all tests…
Creating a very accurate and insightful bug ticket adds a lot of value to the software development process.
The following people on the software development team need to know as much information as possible about software bugs found: Project managers, subject matter experts, software developers, and software test engineers.
Software bugs have the following adverse effects:
a) Software users stop using the software product
b) Software users create a bad reputation for the software product and the company
c) Software users have issues using the software product
d) Software users cannot use a feature in the software program
e) Software development team suddenly changes daily…
The internet and books on software testing are full of information on different types of bugs.
The information is too general and does not help you to recognize a bug in the software program.
The examples below will give you a good feel of what a software bug is.
The examples are close to realistic and presented to people new to software quality assurance.
I) Simple Test Examples
a) A Value entered on the screen is not saved
b) The program only saves the first five input characters into the text box
c) The document starting from the second page…
In the software development environment, project managers, business matter experts, software developers, and software quality assurance experts can all find bugs in the software program.
Software developers find software bugs when:
a) Adding new code changes
b) Fixing a bug
c) Changing existing behavior
d) Reviewing code for refactoring
e) Reviewing code to improve performance
f) Code change peer review
g) Reviewing changes included in the most recent update
Business matter experts or project managers find bugs when:
a) Writing software requirements document
b) Reviewing changes users want to implement in a software release
c) Writing an online help
A software bug is the software behavior that is different from the expected software behavior.
The software requirements document describes the expected software behavior for the new functionality and online help for the existing functionality.
The software bug occurs as the result of:
1) The software requirements document providing inaccurate statements about software behavior, having logical errors in software behavior, using wrong fields from a database, and omitting key aspects for coding review
2) The software requirements should take into consideration new code changes and the impact on the existing functionality.
3) Software development errors:
1. Adding new functionality
2. Fixing another…