-
Notifications
You must be signed in to change notification settings - Fork 275
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #508 from tverhoken/gh-pages
Ajout de Thomas VERHOKEN
- Loading branch information
Showing
1 changed file
with
27 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18421,8 +18421,34 @@ var data = { | |
tags: ['JavaScript', 'TypeScript', 'Angular'], | ||
lang: ['fr'], | ||
}, | ||
], | ||
] | ||
}, | ||
{ | ||
since: "2023-11-16", | ||
name: "Thomas VERHOKEN", | ||
bio: "Développeur éclectique et polyglotte.", | ||
picture: "https://avatars.githubusercontent.com/u/3036052", | ||
cities: ["Lille"], | ||
contacts: { | ||
twitter: "tverhoken", | ||
mail: "[email protected]" | ||
}, | ||
sessions: [ | ||
{ | ||
title: "Mutation testing - Tester vos test ?!?", | ||
abstract: "En tant que développeur.se professionnel.le, vous êtes amené.e.s à tester ce que vous produisez. Mais êtes-vous certain.e.s de la fiabilité des tests que vous écrivez ? Pour vérifier cela, devons-nous aller jusqu’à tester les tests que l’on écrit ?!? Cela serait fastidieux. Et bien voyons ensemble comment faire cela, mais de façon automatisée, au travers de « mutation testing ». Ensemble, voyons en quoi consiste cette pratique et ce qu’elle peut apporter à vos projets ou à vous mêmes.", | ||
tags: ['Tests', 'T.D.D'], | ||
lang: ['fr'] | ||
} | ||
], | ||
location: 'Lille', | ||
websites: [ | ||
{ | ||
name: "Github", | ||
url: "https://github.com/tverhoken" | ||
} | ||
] | ||
} | ||
], | ||
cities: { | ||
'Aix-en-Provence': { | ||
|