Selected Topic Tool based SW-Engineering

Tools to support the Software Life Cycle in general - Branching, Merging, and others - Working With Source Control - Tasks, Impediments, Bugs - Manage the work - Working with tools to plan the work - Working with holistic tools

Tools to support the Software Life Cycle in general - Branching, Merging, and others - Working With Source Control - Tasks, Impediments, Bugs - Manage the work - Working with tools to plan the work - Working with holistic tools

18

0.0 (0)

S. F.

Étudier

S. F.

À propos de ce fichier

This flashcard set covers university-level software engineering tools and practices, focusing on testing, version control systems, and collaboration tools. It delves into various testing methods like exploratory and manual testing, the differences between centralized and distributed version control systems, and the pros and cons of tools like Bitbucket, GitHub, and SVN. The flashcards are beneficial for university students and professionals in software engineering who need to understand the tools and techniques for effective software development and team collaboration.

Cartes-fiches

18

Utilisateurs

5

Langue

Anglais

Catégorie

Informatique

Niveau

Université

Créé / Mis à jour

26.09.2016 / 10.11.2016

Fichiers de cartes similaires

What does push and pull mean?

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

Push: sending changes to another repo
Pull: loading a change from another repo

What types of manual testing are there?

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

Planned manual testing. Manual testing by organizing tests into test plans and test suites by designated testers and test leads.
User acceptance testing. Testing carried out by designated user acceptance testers to verify the value delivered meets customer requirements, while reusing the test artifacts created by engineering teams.
Exploratory testing. Testing carried out by development teams, including developers, testers, UX teams, product owners and more, by exploring the software systems without using test plans or test suites.
Stakeholder feedback. Testing carried out by stakeholders outside the development team, such as users from marketing and sales divisions.

1 / 18

Cartes-fiches

What does push and pull mean?

Push: sending changes to another repo
Pull: loading a change from another repo

What types of manual testing are there?

Planned manual testing. Manual testing by organizing tests into test plans and test suites by designated testers and test leads.
User acceptance testing. Testing carried out by designated user acceptance testers to verify the value delivered meets customer requirements, while reusing the test artifacts created by engineering teams.
Exploratory testing. Testing carried out by development teams, including developers, testers, UX teams, product owners and more, by exploring the software systems without using test plans or test suites.
Stakeholder feedback. Testing carried out by stakeholders outside the development team, such as users from marketing and sales divisions.

Étudier