Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reschedule the presentation to week3: Automation Testing #396

Merged
merged 10 commits into from
Mar 23, 2020
Merged

Reschedule the presentation to week3: Automation Testing #396

merged 10 commits into from
Mar 23, 2020

Conversation

MDRezaulHasan
Copy link

In week3 I want to present a Test automation topic.

@gluckzhang
Copy link

Hi @MDRezaulHasan , as you are going to reschedule your presentation to week3, you should move week2/mrhasa to folder week3 (mv ... then commit). In the current PR you created folder mrhasa in both week2 and week3.

@gluckzhang gluckzhang changed the title For presenting test automation topic Reschedule the presentation to week3: Automation Testing Mar 21, 2020
@gluckzhang gluckzhang self-assigned this Mar 21, 2020
@gluckzhang gluckzhang merged commit a29e1e0 into KTH:master Mar 23, 2020
@gluckzhang gluckzhang added the presentation One of the task categories listed in README.md label Mar 24, 2020
@gluckzhang
Copy link

Hi @MDRezaulHasan , you will give the presentation next. Please note that the current title (automation testing) is too general, you should focus on a concrete topic in automation testing. For example:

  • automation testing -> too generic | an introduction to the most popular automation testing frameworks -> good
  • unit testing -> too generic | unit testing on web applications -> good

Please update the README before next lecture, when you submit your slides :)

@MDRezaulHasan
Copy link
Author

MDRezaulHasan commented Mar 26, 2020 via email

@gluckzhang
Copy link

@MDRezaulHasan , thanks! In order to be merged into master, you should submit another PR. Preferably pulling the updates into your forked repo (or simply forking it again) -> creatig a specific branch -> add the updates and create a PR.

@MDRezaulHasan
Copy link
Author

MDRezaulHasan commented Mar 26, 2020 via email

@gluckzhang
Copy link

Hi @MDRezaulHasan , sorry because the PR has been merged, I missed the update notification.

I think the easies way to do that is: directly modify your README on the webpage on this repo, and choose "Create a new branch for this commit and start a pull request." at the bottom of that page.

@MDRezaulHasan
Copy link
Author

MDRezaulHasan commented Mar 30, 2020 via email

@gluckzhang
Copy link

@MDRezaulHasan you will present it tomorrow using zoom as usual. The streaming url of the lecture will be announced in advance here: #316

@MDRezaulHasan
Copy link
Author

MDRezaulHasan commented Mar 30, 2020 via email

@MDRezaulHasan
Copy link
Author

MDRezaulHasan commented Mar 30, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
presentation One of the task categories listed in README.md
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants